SGRC Daily Cyber Brief - 04 Nov 2026

Read sourced cyber advisories and next steps, or connect your agent to check which entries match your software.

Issue date
Reference
SGRC-DCB-20261104
Last updated
Source checks recorded
Entries
41

Bottom line

  • What is listed. 7 of 41 entries are on CISA's Known Exploited Vulnerabilities list.
  • Past deadline. 6 entries have passed the US federal due date. The oldest was August 6, 2026.
  • Next deadline. 1 entry is still ahead of the US federal due date. The next is November 6, 2026.
  • Fix status. 39 of 41 entries list a fixed version in these records. Not listed does not mean no fix exists, so check the vendor advisory.
  • Canada. No entry carries a cited Canadian source. That does not establish that Canadian organizations are unaffected.

Findings

Open a row for affected versions, fix steps, checks and sources.

41 of 41 entries

Sorted by Issue order (Canada first).

  1. Number 1Siemens Software CenterCVE-2026-110936This could allow an authenticated local attacker to place a specially crafted DLL in a directory that the application searches, leading to arbitrary code execution with the privileges of the affected application.CVSS 8.4EPSS 1.0%Deadline passedCISA due Nov 3, 2026, passed

    What happened

    This could allow an authenticated local attacker to place a specially crafted DLL in a directory that the application searches, leading to arbitrary code execution with the privileges of the affected application.

    How to fix

    1. Upgrade Siemens Software Center to 4.0.9.8 or later (fixed versions per the NVD record).
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-03.
    3. Follow the vendor advisory: https://cert-portal.siemens.com/productcert/html/ssa-580366.html

    How to check

    Vendor guidance: "Indicators of Compromise" section at https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/

    Affected versions

    • before 4.0.9.8

    Fixed versions

    • 4.0.9.8

    Risk record

    Response
    Immediate
    Added to KEV
    Oct 20, 2026

    Sources

  2. Number 2Plex Media ServerCVE-2026-96655Plex Media Server before 1.43.3.10861 allows an authenticated user to request arbitrary internal or external addresses via the '/video/:/transcode/universal' path parameter.CVSS 5.3EPSS 1.6%Deadline passedCISA due Nov 3, 2026, passed

    What happened

    Plex Media Server before 1.43.3.10861 allows an authenticated user to request arbitrary internal or external addresses via the '/video/:/transcode/universal' path parameter.

    How to fix

    1. Upgrade Plex Media Server to 1.43.3.10861 or later (fixed versions per the NVD record).
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-03.

    How to check

    Network detection: ET Open Suricata rule sid 2072511 in https://rules.emergingthreats.net/open/suricata-7.0/emerging-all.rules (community rule; test before use).

    Affected versions

    • before 1.43.3.10861

    Fixed versions

    • 1.43.3.10861

    Risk record

    Response
    Immediate
    Added to KEV
    Oct 20, 2026

    Sources

  3. Number 3Plex Media ServerCVE-2026-96652Plex Media Server before 1.43.3.10861 allows SSRF via '/player/timeline'. An attacker using any X-Plex-Token value can include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination.CVSS 5.3EPSS 11.9%Deadline passedCISA due Nov 3, 2026, passed

    What happened

    Plex Media Server before 1.43.3.10861 allows SSRF via '/player/timeline'. An attacker using any X-Plex-Token value can include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination.

    How to fix

    1. Upgrade Plex Media Server to 1.43.3.10861 or later (fixed versions per the NVD record).
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-03.

    How to check

    Network detection: ET Open Suricata rule sid 2072509 in https://rules.emergingthreats.net/open/suricata-7.0/emerging-all.rules (community rule; test before use).

    Affected versions

    • before 1.43.3.10861

    Fixed versions

    • 1.43.3.10861

    Risk record

    Response
    Immediate
    Added to KEV
    Oct 20, 2026

    Sources

  4. Number 4N-able N-centralCVE-2026-18577An incomplete patch for CVE-2026-18556 allows for authentication bypass and account takeover in N-central Versions through 2026.3.1.CVSS 8.1EPSS 14.6%Deadline passedCISA due Aug 6, 2026, passed

    What happened

    An incomplete patch for CVE-2026-18556 allows for authentication bypass and account takeover in N-central Versions through 2026.3.1.

    How to fix

    1. No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-08-06.
    3. Follow the vendor advisory: https://www.n-able.com/blog/n-central-security-update-august-2-2026
    4. Vendor patch or mitigation reference: https://documentation.n-able.com/N-central/Release_Notes/GA/Content/N-central_2026.3_HF1_Release_Notes.htm
    5. Generic hardening for CWE-288 (Authentication Bypass Using an Alternate Path or Channel), from the MITRE CWE catalog. This is general weakness guidance, not a vendor fix or workaround for this CVE. Phase: Architecture and Design. Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

    How to check

    Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-18577.yaml (community template; tests exposure, not compromise).

    Affected versions

    • before 2026.3
    • 2026.3

    Risk record

    Response
    Immediate
    Added to KEV
    Aug 3, 2026

    Sources

  5. Number 5N-able N-centralCVE-2026-18556Authentication bypass using an alternate path or channel vulnerability in N-able N-central allows Authentication Bypass.CVSS 7.4EPSS 7.9%Deadline passedCISA due Aug 7, 2026, passed

    What happened

    Authentication bypass using an alternate path or channel vulnerability in N-able N-central allows Authentication Bypass.

    How to fix

    1. No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-08-07.
    3. Follow the vendor advisory: https://uptime.n-able.com/
    4. Generic hardening for CWE-288 (Authentication Bypass Using an Alternate Path or Channel), from the MITRE CWE catalog. This is general weakness guidance, not a vendor fix or workaround for this CVE. Phase: Architecture and Design. Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

    Affected versions

    • through 2026.1

    Risk record

    Response
    Immediate
    Added to KEV
    Aug 4, 2026

    Sources

  6. Number 6Microsoft SharePointCVE-2026-55040Widely deployedWeak authentication in Microsoft Office SharePoint allows an unauthorized attacker to bypass a security feature over a network.CVSS 9.1EPSS 69.5%Deadline passedCISA due Aug 21, 2026, passed

    What happened

    Weak authentication in Microsoft Office SharePoint allows an unauthorized attacker to bypass a security feature over a network.

    How to fix

    1. Upgrade Microsoft SharePoint to 16.0.19725.20434 or later (fixed versions per the NVD record).
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-08-21.
    3. Follow the vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55040

    How to check

    Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/javascript/cves/2026/CVE-2026-55040.yaml (community template; tests exposure, not compromise).

    Network detection: ET Open Suricata rule sid 2071485 in https://rules.emergingthreats.net/open/suricata-7.0/emerging-all.rules (community rule; test before use).

    Affected versions

    • before 16.0.19725.20434
    • 2016
    • 2019

    Fixed versions

    • 16.0.19725.20434

    Risk record

    Response
    Immediate
    Added to KEV
    Aug 18, 2026

    Sources

  7. Number 7WordPress WordPress CoreCVE-2026-119977This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.CVSS 8.1EPSS 1.0%Deadline aheadCISA due Nov 6, 2026

    What happened

    This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.

    How to fix

    1. Upgrade WordPress WordPress Core to the fixed release for your branch: 4.7.39, 4.8.34, 4.9.35, 5.0.31, 5.1.28, 5.2.30, 5.3.27, 5.4.25, 5.5.24, 5.6.23, 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, 6.6.11, 6.7.11, 6.8.12, 6.9.11, 7.0.8, 7.1.4 or later (fixed versions per the NVD record).
    2. CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-06.

    Affected versions

    • 4.7 up to, not including, 4.7.39
    • 4.8 up to, not including, 4.8.34
    • 4.9 up to, not including, 4.9.35
    • 5.0 up to, not including, 5.0.31
    • 5.1 up to, not including, 5.1.28
    • 5.2 up to, not including, 5.2.30
    • 5.3 up to, not including, 5.3.27
    • 5.4 up to, not including, 5.4.25
    • 5.5 up to, not including, 5.5.24
    • 5.6 up to, not including, 5.6.23
    • 5.7 up to, not including, 5.7.21
    • 5.8 up to, not including, 5.8.19
    • 5.9 up to, not including, 5.9.20
    • 6.0 up to, not including, 6.0.18
    • 6.1 up to, not including, 6.1.16
    • 6.2 up to, not including, 6.2.15
    • 6.3 up to, not including, 6.3.14
    • 6.4 up to, not including, 6.4.14
    • 6.5 up to, not including, 6.5.14
    • 6.6 up to, not including, 6.6.11
    • 6.7 up to, not including, 6.7.11
    • 6.8 up to, not including, 6.8.12
    • 6.9 up to, not including, 6.9.11
    • 7.0 up to, not including, 7.0.8
    • 7.1 up to, not including, 7.1.4

    Fixed versions

    • 4.7.39
    • 4.8.34
    • 4.9.35
    • 5.0.31
    • 5.1.28
    • 5.2.30
    • 5.3.27
    • 5.4.25
    • 5.5.24
    • 5.6.23
    • 5.7.21
    • 5.8.19
    • 5.9.20
    • 6.0.18
    • 6.1.16
    • 6.2.15
    • 6.3.14
    • 6.4.14
    • 6.5.14
    • 6.6.11
    • 6.7.11
    • 6.8.12
    • 6.9.11
    • 7.0.8
    • 7.1.4

    Risk record

    Response
    Immediate
    Added to KEV
    Nov 3, 2026

    Sources

  8. Number 8google chromeCVE-2026-120931Out of bounds write in WebGL in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Out of bounds write in WebGL in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 156.0.8078.47 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html

    Affected versions

    • before 156.0.8078.47

    Fixed versions

    • 156.0.8078.47

    Risk record

    Response
    Immediate

    Sources

  9. Number 9google chromeCVE-2026-121249Buffer overflow in ANGLE in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Buffer overflow in ANGLE in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  10. Number 10google chromeCVE-2026-121247Buffer overflow in Dawn in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Buffer overflow in Dawn in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  11. Number 11google chromeCVE-2026-121246Use after free in WebGL in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in WebGL in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  12. Number 12google chromeCVE-2026-121241Use after free in Navigation in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Use after free in Navigation in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  13. Number 13google chromeCVE-2026-121234Privilege elevation in Contacts in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Privilege elevation in Contacts in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  14. Number 14google chromeCVE-2026-121229Memory corruption in ANGLE in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Memory corruption in ANGLE in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  15. Number 15google chromeCVE-2026-121214Use after free in Passwords in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in Passwords in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  16. Number 16google chromeCVE-2026-121202Use after free in Autofill in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Use after free in Autofill in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  17. Number 17google chromeCVE-2026-121200Incorrect reference resolution in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Incorrect reference resolution in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  18. Number 18google chromeCVE-2026-121189Use after free in Browser in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in Browser in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  19. Number 19google chromeCVE-2026-121185Use after free in PictureInPicture in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in PictureInPicture in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  20. Number 20google chromeCVE-2026-121156Buffer overflow in Dawn in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Buffer overflow in Dawn in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  21. Number 21google chromeCVE-2026-121148Use after free in ANGLE in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in ANGLE in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  22. Number 22google chromeCVE-2026-121131Use after free in Mobile in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted Chrome extension. (Chromium security severity: High).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Use after free in Mobile in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted Chrome extension. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  23. Number 23google chromeCVE-2026-121126Use after free in Core in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in Core in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  24. Number 24google chromeCVE-2026-121114Use after free in TabStrip in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in TabStrip in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  25. Number 25google chromeCVE-2026-121104Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  26. Number 26google chromeCVE-2026-121089Use after free in WebGPU in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in WebGPU in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  27. Number 27google chromeCVE-2026-121086Buffer overflow in Skia in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Buffer overflow in Skia in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  28. Number 28google chromeCVE-2026-121077Use after free in Mobile in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Use after free in Mobile in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  29. Number 29google chromeCVE-2026-121076Use after free in WebXR in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.3%Widely deployedCISA due None

    What happened

    Use after free in WebXR in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  30. Number 30google chromeCVE-2026-121074Memory corruption in GPU in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Memory corruption in GPU in Google Chrome on on Android prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  31. Number 31google chromeCVE-2026-121071Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  32. Number 32google chromeCVE-2026-121060Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  33. Number 33Google ChromeCVE-2026-121037Out of bounds write in ANGLE in Google Chrome on on Windows prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Out of bounds write in ANGLE in Google Chrome on on Windows prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade Google Chrome to 157.0.8103.38 or later (fixed versions per the CVE record).

    Affected versions

    • 157.0.8103.38 up to, not including, 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  34. Number 34google chromeCVE-2026-121035Use after free in Prerender in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in Prerender in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  35. Number 35Google ChromeCVE-2026-121034Use after free in Views in Google Chrome on on Windows prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Use after free in Views in Google Chrome on on Windows prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High).

    How to fix

    1. Upgrade Google Chrome to 157.0.8103.38 or later (fixed versions per the CVE record).

    Affected versions

    • 157.0.8103.38 up to, not including, 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  36. Number 36google chromeCVE-2026-121030Incorrect authorization in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).CVSS 9.6EPSS 0.4%Widely deployedCISA due None

    What happened

    Incorrect authorization in DevTools in Google Chrome prior to 157.0.8103.38 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium).

    How to fix

    1. Upgrade google chrome to 157.0.8103.38 or later (fixed versions per the NVD record).
    2. Follow the vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html

    Affected versions

    • before 157.0.8103.38

    Fixed versions

    • 157.0.8103.38

    Risk record

    Response
    Immediate

    Sources

  37. Number 37WatchGuard AuthPoint Authentication GatewayCVE-2026-121640An Authentication Bypass by Capture-replay vulnerability in WatchGuard AuthPoint Gateway allows an attacker who has observed a legitimate request between AuthPoint Gateway components to replay it and perform unauthorized administrative actions, including disrupting authentication services.CVSS 9.1EPSS Not scoredNew criticalCISA due None

    What happened

    An Authentication Bypass by Capture-replay vulnerability in WatchGuard AuthPoint Gateway allows an attacker who has observed a legitimate request between AuthPoint Gateway components to replay it and perform unauthorized administrative actions, including disrupting authentication services.

    How to fix

    1. Upgrade WatchGuard AuthPoint Authentication Gateway to 7.6.0 or later (fixed versions per the CVE record).
    2. Vendor solution (CVE record): AuthPoint Authentication Gateway 7.6.0

    Affected versions

    • 1.0 up to, not including, 7.6.0

    Fixed versions

    • 7.6.0

    Risk record

    Response
    Immediate

    Sources

  38. Number 38WatchGuard AuthPoint Authentication GatewayCVE-2026-121639A Missing Authentication for Critical Function vulnerability in WatchGuard AuthPoint Gateway allows a remote unauthenticated attacker with network access to the AuthPoint Gateway host to disrupt authentication services and delete the local directory synchronization configuration.CVSS 9.2EPSS Not scoredNew criticalCISA due None

    What happened

    A Missing Authentication for Critical Function vulnerability in WatchGuard AuthPoint Gateway allows a remote unauthenticated attacker with network access to the AuthPoint Gateway host to disrupt authentication services and delete the local directory synchronization configuration.

    How to fix

    1. Upgrade WatchGuard AuthPoint Authentication Gateway to 7.6.0 or later (fixed versions per the CVE record).
    2. Vendor solution (CVE record): AuthPoint Authentication Gateway 7.6.0

    Affected versions

    • 1.0 up to, not including, 7.6.0

    Fixed versions

    • 7.6.0

    Risk record

    Response
    Immediate

    Sources

  39. Number 39WatchGuard AuthPoint Authentication GatewayCVE-2026-121638An Improper Certificate Validation vulnerability in WatchGuard AuthPoint Gateway allows an attacker with an on-path network position to intercept and modify communications between the AuthPoint Gateway and local authentication providers.CVSS 9.1EPSS Not scoredNew criticalCISA due None

    What happened

    An Improper Certificate Validation vulnerability in WatchGuard AuthPoint Gateway allows an attacker with an on-path network position to intercept and modify communications between the AuthPoint Gateway and local authentication providers.

    How to fix

    1. Upgrade WatchGuard AuthPoint Authentication Gateway to 7.6.0 or later (fixed versions per the CVE record).
    2. Vendor solution (CVE record): AuthPoint Authentication Gateway 7.6.0

    Affected versions

    • 1.0 up to, not including, 7.6.0

    Fixed versions

    • 7.6.0

    Risk record

    Response
    Immediate

    Sources

  40. Number 40SEPPmail AG SEPPmail Secure Email Gateway (SEG)CVE-2026-114425SEPPmail Secure Email Gateway before 15.1.1 trusts a file path supplied in externally provided Large File Transfer attachment metadata. An unauthenticated remote sender can cause the mail-processing worker to disclose, move, or delete an accessible regular file when LFT is enabled and the message reaches an affected secure-mail processing path.CVSS 9.2EPSS 0.3%New criticalCISA due None

    What happened

    SEPPmail Secure Email Gateway before 15.1.1 trusts a file path supplied in externally provided Large File Transfer attachment metadata. An unauthenticated remote sender can cause the mail-processing worker to disclose, move, or delete an accessible regular file when LFT is enabled and the message reaches an affected secure-mail processing path.

    How to fix

    1. Upgrade SEPPmail AG SEPPmail Secure Email Gateway (SEG) to 15.1.1 or later (fixed versions per the CVE record).

    Affected versions

    • before 15.1.1

    Fixed versions

    • 15.1.1

    Risk record

    Response
    Immediate

    Sources

  41. Number 41SEPPmail AG SEPPmail Secure Email Gateway (SEG)CVE-2026-114424SEPPmail Secure Email Gateway before 15.1.1 can evaluate attacker-influenced replacement text as Perl code in sender or recipient replacement rules.CVSS 9.2EPSS 0.3%New criticalCISA due None

    What happened

    SEPPmail Secure Email Gateway before 15.1.1 can evaluate attacker-influenced replacement text as Perl code in sender or recipient replacement rules.

    How to fix

    1. Upgrade SEPPmail AG SEPPmail Secure Email Gateway (SEG) to 15.1.1 or later (fixed versions per the CVE record).

    Affected versions

    • before 15.1.1

    Fixed versions

    • 15.1.1

    Risk record

    Response
    Immediate

    Sources

Sources

Citations by publisher across this issue. Each row lists its own links. Sources checked November 4, 2026 at 01:15 p.m. EST.

Authorities
  • CVE Program41
  • GitHub Advisory Database41
  • NVD API41
  • CISA KEV7
  • Canadian Centre for Cyber Security1
Vendors
  • google29
  • N-able3
  • Siemens2
  • Microsoft1
Press
  • Rapid73
  • The Hacker News1

Coverage is limited to the entries shown. Canadian context requires cited Canadian evidence; worldwide incident and campaign collection is still being expanded. The JSON Feed includes the matching data and original verification timestamps.