ISC disclosed a remotely exploitable memory-corruption bug in BIND 9's named on Oct 21. An attacker who captures a GSS-TSIG signed UDP message (the Kerberos signing used for Active Directory-style dynamic DNS updates) can replay it while the negotiated key is still valid and, combined with crafted queries to a zone they control, may get remote code execution, or at least crash named. CVSS 8.1 (High). No workaround. Affects BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.29 and 9.21.0 through 9.21.26. Fixed in 9.20.30 and 9.21.27; ISC lists no 9.18 fix. ISC knows of no active exploitation. Debian trixie has a fixed package; Debian bookworm and Ubuntu are still waiting.
2026-10-22: Debian publishes DSA-6576-1 with a fixed bind9 for trixie; bookworm (9.18) is still listed as vulnerable. (source)
2026-10-22: Japan's registry JPRS issues an urgent alert telling BIND operators to upgrade. (source)
2026-10-21: ISC publicly discloses CVE-2026-94300 and ships BIND 9.20.30 and 9.21.27. ISC found it in internal testing; Dave Aitel of OpenAI reported it independently. (source)
Red Hat disclosed a flaw in Keycloak's SAML HTTP-Redirect binding (keycloak-services): the server accepts percent-encoded parameter names such as %53AMLResponse, while the signature check only looks at the literal parameter names. An unauthenticated attacker can use that mismatch to slip in a crafted, unsigned SAML message that Keycloak processes instead of the legitimately signed one, which leads to full takeover of federated user accounts. Red Hat rates it Important with a CVSS 3.1 score of 9.1 and lists the Red Hat Build of Keycloak as affected; Red Hat Single Sign-On 7 is not affected. Keycloak 26.8.2, released on Nov 5 2026, fixes it (the commit "Verify the SAML redirect binding message that is processed" closes CVE-2026-117691); Red Hat had not listed a fixed Red Hat Build of Keycloak release when the CVE was published. No exploitation has been reported.
2026-11-05: Red Hat publishes CVE-2026-117691 (CVSS 3.1 9.1, Important): percent-encoded parameter names skip SAML signature verification, allowing unsigned messages to be processed and federated accounts taken over. Red Hat says no mitigation currently meets its criteria; no fixed version is listed yet. (source)
2026-11-05: Keycloak 26.8.2 is released with the fix (the commit "Verify the SAML redirect binding message that is processed" closes CVE-2026-117691), alongside fixes for other SAML flaws including CVE-2026-110931 and CVE-2026-107602. (source)
2026-10-26: Mayssen Aidoudi (Think-it GmbH) reports the SAML redirect-binding signature bypass to Red Hat. (source)
SonicWall published SNWLID-2026-0014 covering multiple SonicOS flaws. Primary tracked here: CVE-2026-19868, a use-of-single-factor-authentication issue in the SonicOS SSLVPN service that may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls and SAML-enforced MFA (CWE-308). CISA added it to the KEV catalog on 2026-11-06 (due 2026-11-20; ransomware use Unknown). NVD (published 2026-11-06T19:17:48Z by PSIRT@sonicwall.com) lists Gen7 SonicOS 7.3.3-7015 and older and Gen8 8.2.2-8015 and older as affected; no CVSS in NVD yet. Same advisory also covers sibling SonicOS CVEs CVE-2026-82308 (pre-auth SSL-VPN heap overflow DoS), CVE-2026-107154 / CVE-2026-107155 (management interface), CVE-2026-19703 (weak password hashing on virtual appliances), and CVE-2026-77708 / CVE-2026-77709 (pre-auth TACACS+ buffer overflows). Confirm fixed builds on the vendor advisory.
Fixed in
See SNWLID-2026-0014 for fixed SonicOS builds; NVD lists Gen7 newer than 7.3.3-7015 and Gen8 newer than 8.2.2-8015 as outside the affected range
2026-11-06: SonicWall PSIRT publishes SNWLID-2026-0014; NVD receives CVE-2026-19868 (SSLVPN SAML/MFA bypass via alternate auth) and sibling SonicOS CVEs CVE-2026-82308, CVE-2026-107154, CVE-2026-107155, CVE-2026-19703, CVE-2026-77708, CVE-2026-77709. Affected: Gen7 7.3.3-7015 and older; Gen8 8.2.2-8015 and older. (source)
2026-11-06: CISA adds CVE-2026-19868 to the Known Exploited Vulnerabilities Catalog (due 2026-11-20; known ransomware use Unknown). Required action: apply vendor mitigations per BOD 26-04. (source)
Erica Windisch of Cyberdione Labs published Tailworm, 11 lab-reproduced findings in Tailscale v1.104.2 and headscale v0.29.5 without coordinated disclosure. The main one: with Tailscale SSH enabled, unix-socket port forwarding runs as root, so anyone with one approved device and an SSH rule can reach root on the target and capture enrollment keys. Others cover experimental app connectors bypassing ACLs (cloud metadata, internal LANs), a tailscale serve forward to the local API, and headscale/DERP memory exhaustion. Tailscale confirmed the SSH issues as serious privilege-escalation bugs and on Oct 28 released Tailscale 1.104.4 with bulletins TS-2026-014 (SSH unix-socket forwarding to root-only sockets such as the Docker socket or local API), TS-2026-015 (SSH session memory exhaustion), TS-2026-016 (serve unix backends reaching privileged sockets) and TS-2026-017 (HTTP/2 serve capability mix-up). Upgrade to 1.104.4 or newer; the bulletins do not cover the app-connector or headscale findings. It is lateral movement from a foothold, not internet RCE.
Fixed in
tailscale 1.104.4, headscale 0.29.7 (control server; nodes still need Tailscale v1.104.4+)
Latest updates (3)
2026-10-30: Headscale, the open-source Tailscale control server, ships 0.29.7 as a security release fixing Tailworm findings and issues from Anthropic's oss-scanner (none critical, some can cause denial of service). It recommends upgrading to Headscale 0.29.7 and Tailscale v1.104.4 or newer, noting the SSH fixes run in tailscaled on each node, so upgrading Headscale alone does not apply them. (source)
2026-10-28: Tailscale releases v1.104.4 and publishes TS-2026-014 (Tailscale SSH unix-socket forwarding ran as root and could reach root-only sockets such as the Docker socket or the tailscaled local API), TS-2026-015 (SSH session memory exhaustion DoS), TS-2026-016 (serve unix backends could reach privileged sockets, including the local API) and TS-2026-017 (HTTP/2 serve could mix up Tailscale-App-Capabilities across mounts), all fixed in 1.104.4. Mitigation if you can't upgrade: TS_SSH_DISABLE_FORWARDING=1. (source)
2026-10-27: SecurityWeek reports the Tailworm report was updated on Oct 27 to say fixes for several findings have landed in Tailscale's public code repositories, but none is in a numbered release yet; Tailscale still targets a patched client by the end of Oct 27 and neither side reports exploitation in the wild. (source)
CVE-2026-83844 is an out-of-bounds read in Microsoft Paint that Microsoft rates Important with CVSS 8.1. It can allow remote code execution over a network with no sign-in and no user interaction, at high attack complexity. Microsoft published the issue on Oct 13 2026 as a Microsoft Store security update, not a Windows Update. The public CVE record still lists Paint as affected below 11.2605.91.0, while MSRC remediation names fixed build 11.2609.401.0 — scanners that trust only the CVE range may wrongly clear older Store builds. As of Nov 6 2026, The Hacker News and RFF reported that Store catalogs in multiple countries were serving 11.2609.401.0. Admins should inventory every user copy and the provisioned package and update Paint through the Store (or MDM Store-app update scans) to 11.2609.401.0 or later. Not known to be exploited or publicly disclosed at Microsoft's publication; not in CISA KEV when THN checked Nov 6.
Fixed in
Microsoft Paint 11.2609.401.0 or later via Microsoft Store (not Windows Update)
2026-11-06: The Hacker News and RFF report Microsoft Store now offering Paint 11.2609.401.0 in checked markets; Windows Update still does not deliver the fix. (source)
2026-11-05: RFF reports Store catalogs in multiple countries still topping out at Paint 11.2605.81.0, below the MSRC-named fixed build 11.2609.401.0. (source)
2026-10-13: Microsoft publishes CVE-2026-83844 for a Paint out-of-bounds read RCE delivered as a Store security update. (source)
Google's Chrome 156 stable release (156.0.8078.47, .48 on some Windows/Mac) fixed 353 security issues, including six critical bugs in Skia, Accessibility, CSS, Paint and WebRTC. On Oct 27 a follow-up update (156.0.8078.73/.74) fixed 52 more, four of them critical (FileSystem, FileAPI, Skia, Layout). On Oct 29 a third update (156.0.8078.79/.80) fixed 21 more, including a critical memory corruption bug in MediaStream (CVE-2026-76024). Google has not said any are exploited. The rollout is staged, so update and relaunch rather than waiting.
2026-10-29: Chrome 156.0.8078.79/.80 fixes 21 more security bugs, one critical (CVE-2026-76024, memory corruption in MediaStream) and 19 high; none reported exploited. (source)
2026-10-28: Anthropic says an unreleased Claude model found 62 of the Chrome flaws fixed as of Chrome 156 (all critical or high, 13 sandbox escapes) and chained four into a one-click sandbox escape; lab-built, not seen in attacks. (source)
2026-10-27: Chrome 156.0.8078.73/.74 fixes 52 more security bugs, four critical (FileSystem, FileAPI, Skia, Layout); none reported exploited. (source)
Craft CMS published four security advisories fixed in 4.18.9 and 5.11.2 (and 5.11.2-only for one). CVE-2026-123488 is an unauthenticated SQL injection in the element search endpoint (CVSS 9.8) that lets remote attackers read/write the database and escalate to admin. CVE-2026-123491 is unauthenticated GraphQL eager-load SQLi (8.2). CVE-2026-123489 is control-panel blind SQLi via getNext/getPrev (7.1). CVE-2026-123490 is authenticated privilege escalation via getOwners() sandbox criteria (8.8, Craft 5.8.17–before 5.11.2). Upgrade to 4.18.9 or 5.11.2.
2026-11-06: NVD publishes CVE-2026-123488 (CVSS 9.8) describing unauthenticated SQLi via the attribute parameter on the element search endpoint. (source)
FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager contain a path traversal vulnerability that may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands. Added to CISA KEV on 2026-10-16.
Gitea 28.3.0 (third maintenance release of the 28 series) ships a large security batch. CVE-2026-120263: when ACCOUNT_LINKING=auto and registration is enabled, the link-account sign-up form looked up the account to link by attacker-submitted username/email instead of the OAuth2 identity, allowing passwordless takeover of existing accounts. The release also fixes high-severity Actions issues (fork workflows obtaining secrets/write tokens via review commit_id; Actions task tokens authenticating to the REST API without scope), stored XSS via artifact Content-Encoding, write-collaborator release/milestone/label destruction on archived repos, and additional medium issues around token scopes. Gitea strongly recommends upgrading ASAP. Fixed in 28.3.0.
2026-11-01: Gitea publishes multiple security advisories for the 28.3.0 release, including GHSA-8p3x-w464-4g6v (OAuth2 account linking) and high-severity Actions/token issues. (source)
2026-11-01: Gitea blog: Release of 28.3.0 documents CVE-2026-120263 and related security fixes; strongly recommends upgrading. (source)
NVD published four JupyterLab Desktop CVEs on 2026-11-06 for issues patched in the Jul 22 2026 v4.6.2-1 security release (first Desktop release in two years). Two are critical remote code execution: CVE-2026-102530 (CVSS 9.4) — unsanitized remote-server URLs in the Connect dialog / Welcome view enable XSS that abuses the privileged Electron IPC bridge; and CVE-2026-86044 (CVSS 9.6) — a MathJax link in an untrusted notebook plus a getServerInfo IPC leak lets one click hand the local Jupyter server token to an attacker site for RCE (requires JupyterLab < 4.4.8 in the managed environment). Two medium macOS-only TCC bypasses (CVE-2025-54991 / CVE-2025-55002, CVSS 5.5) need existing local code execution. Affected: Desktop <= v4.2.5-1. Upgrade to 4.6.2-1.
Fixed in
JupyterLab Desktop 4.6.2-1, Partial workaround for CVE-2026-86044: upgrade JupyterLab in-environment to >= 4.4.8
2026-11-06: NVD receives CVE-2026-102530 (CVSS 9.4), CVE-2026-86044 (CVSS 9.6), CVE-2025-54991 and CVE-2025-55002 (both CVSS 5.5) from security-advisories@github.com, linking the Jul 2026 Desktop security release. (source)
2026-07-24: GitHub Security Advisories published for the four Desktop issues (CVE assignment noted as pending at the time for the two critical RCE advisories). (source)
2026-07-22: JupyterLab Desktop v4.6.2-1 released with patches for GHSA-vrj4-r4fw-9rfh (XSS→RCE via Connect URL), GHSA-2mr8-962v-wc67 (one-click token leak→RCE), GHSA-8cvf-4977-r95v (CVE-2025-54991 TCC), and GHSA-5c3f-5gj7-p9xh (CVE-2025-55002 TCC). (source)
On Nov 6 2026 Canonical published a wave of critical LXD advisories (CVSS 9.9) for host escapes. Already tracked: GHSA-jpf8-86f3-wp38 / CVE-2026-48752 (templates/ symlink AFRW) and GHSA-9j25-mm2h-2f76 / CVE-2026-48750 (exec-output symlink AFW). Same-day additions: GHSA-vghh-5rfx-xhq8 / CVE-2026-48749 (rootfs/ symlink AFRW in a crafted image); GHSA-pjff-c2wc-f6jm / CVE-2026-48769 (arbitrary file write via trusted Incus-Image-Hash path traversal on source.type=url downloads); GHSA-fmc8-p6q7-75cc / CVE-2026-48755 (backup compression_algorithm argument injection leading to AFW/ACE). All were reported from the Incus fork. Fixes are in the github.com/canonical/lxd Go module; upgrade to fixed builds that include the advisory commits / firstPatched versions. Also folded GHSA-47w9-6r3f-938g / CVE-2026-48751: instance snapshots ignore `restricted.containers.lowlevel=block`, allowing abuse of raw.lxc / raw.qemu hooks for host ACE after moving a crafted snapshot into a restricted project; LXD >= 4.12 affected; patched in 6.9 / 5.21.5 / 5.0.7 (reported from Incus GHSA-48q5-w887-33wv; originally published Jun 26 2026, resurfaced in the Nov 6 critical GHSA wave). Further folded high-severity project-restriction bypasses GHSA-7mr3-28h5-m5vx (custom volume copy across projects) and GHSA-qx75-2p3r-pwm5 (instance copy across projects): authenticated caller knowing source project/volume or instance names can copy secrets they should not view; LXD >= 4.12; patched in 5.0.7 / 5.21.5 / 6.8 (note 6.8, not only 6.9); GHSA firstPatched Go module 0.0.0-20260630083100-c5184be310b1; reported from Incus GHSA-64f3-v33m-w89f and GHSA-c9f5-j9c3-mhrg; no CVE IDs assigned on the GitHub Advisory records as of this fold.
Fixed in
github.com/canonical/lxd 0.0.0-20260203144152-d1c8ba15d160 or later (templates/ fix per GHSA-jpf8-86f3-wp38), github.com/canonical/lxd 0.0.0-20260626085134-124f90100640 or later (exec-output fix per GHSA-9j25-mm2h-2f76), github.com/canonical/lxd 0.0.0-20260630083100-c5184be310b1 or later (GHSA-vghh-5rfx-xhq8 / GHSA-pjff-c2wc-f6jm / GHSA-fmc8-p6q7-75cc / GHSA-47w9-6r3f-938g / GHSA-7mr3-28h5-m5vx / GHSA-qx75-2p3r-pwm5), lxd-5.21.5 referenced by GHSA-9j25-mm2h-2f76; upgrade to fixed LXD releases that include the advisory commits, LXD 6.9, 5.21.5, 5.0.7 (GHSA-47w9-6r3f-938g / CVE-2026-48751 restricted project bypass), LXD 6.8, 5.21.5, 5.0.7 (GHSA-7mr3-28h5-m5vx / GHSA-qx75-2p3r-pwm5 project restriction bypasses; note 6.8 for these High advisories)
2026-11-06: Canonical publishes GHSA-9j25-mm2h-2f76 (CVE-2026-48750): arbitrary file write on host via exec-output symlink in a crafted image; CVSS 9.9; firstPatched Go module 0.0.0-20260626085134-124f90100640; references lxd-5.21.5 and Incus GHSA-73hr-m85f-64v9. (source)
2026-11-06: Canonical publishes GHSA-jpf8-86f3-wp38 (CVE-2026-48752): arbitrary file read+write on host via templates/ symlink in a malicious image; CVSS 9.9; firstPatched Go module 0.0.0-20260203144152-d1c8ba15d160; reported from Incus GHSA-vxp5-584q-c479. (source)
2026-11-06: Canonical publishes GHSA-vghh-5rfx-xhq8 (CVE-2026-48749): host AFRW via rootfs/ symlink in a malicious image; CVSS 9.9; firstPatched Go module 0.0.0-20260630083100-c5184be310b1. (source)
A heap buffer overflow in Pillow's FlashPix (FPX) JPEG-tile decoder lets an attacker run code by getting an application to open a single crafted file with Image.open(). Pillow detects FPX files by their OLE2 content, not their extension, so any service that opens or thumbnails untrusted uploads with the optional olefile package installed can be hit with no user interaction. The advisory includes a working proof of concept (shown on Pillow 12.2.0 with ASLR disabled). Pillow 12.3.0 and earlier are affected; upgrade to 13.0.0. GitHub rates it critical (CVSS 4.0 score 9.2). The same 13.0.0 release (Oct 16) also fixes other critical bugs: CVE-2026-112900, where an EPS filename starting with - or @ is passed to Ghostscript as an option and can lead to code execution (2.6.0 through 12.3.0); CVE-2026-112393, a heap overflow when saving TIFF to BytesIO (public reproducer); and CVE-2026-112403, a JPEG heap overflow with draft()/thumbnail() on libjpeg-turbo 3.x builds.
2026-10-23: Pillow publishes GHSA-5x8w-8jj5-q52h (CVE-2026-112398) with a proof of concept; the fix ships in Pillow 13.0.0. (source)
2026-10-23: GitHub publishes GHSA-w889-685w-c8fh (CVE-2026-112900): attacker-controlled EPS filenames beginning with - or @ are parsed as Ghostscript options, potentially RCE even with -dSAFER; fixed in 13.0.0. (source)
2026-10-16: Pillow 13.0.0 is released with fixes for several critical bugs, including CVE-2026-112900 (Ghostscript argument injection via EPS filenames), CVE-2026-112393 (TIFF save to BytesIO heap overflow) and CVE-2026-112403 (JPEG draft-scale heap overflow). (source)
Ruby released 4.0.9, 3.4.12 and 3.3.13 on Oct 23 2026 to fix bugs in its Onigmo regular-expression engine (a double free and integer overflows) that GitLab turned into remote code execution on its servers, tracked by GitLab as CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264. Any Ruby app that compiles a regex from an attacker-controlled string (Regexp.new, Regexp.union, Regexp.compile or /#{input}/) is exposed; Regexp.timeout and pattern-length limits do not protect. Apps that only use their own hard-coded regexes are not affected. Ruby 3.2 and older are end-of-life and get no fix.
2026-10-30: Rapid7 merges a Metasploit exploit module for CVE-2026-97229 (GitLab RCE via the CI Lint endpoint), making a ready-made public exploit available. Patch GitLab and, for self-built installs, Ruby now. (source)
2026-10-29: CISA adds CVE-2026-97229 (GitLab CE/EE integer overflow or wraparound) to its Known Exploited Vulnerabilities catalog, confirming exploitation in the wild. GitLab 19.4.2, 19.3.5 and 19.2.8 or later fix it. (source)
2026-10-29: Alpine Linux reopens its GitLab, upgraded to 19.3.7 after the rebuild; users must set a new password and accept new SSH host key fingerprints. (source)
INCIBE-CERT coordinated disclosure of seven vulnerabilities in TPC Software's MatchPoint sports-facility management platform (INCIBE-2026-841, posted 2026-11-05). Three are critical: CVE-2026-111489 (CVSS v4 9.9) — a static credential embedded in the mobile app that returns an 'autorizado' token granting unauthenticated API access; CVE-2026-111490 (CVSS v4 9.9) — IDOR via the actingasuser HTTP header letting attackers reach personal, banking, and financial data, private messages, physical-access QR codes, and perform account takeover / balance transfers; CVE-2026-111494 (CVSS v4 9.1) — Android TrustManager accepts any TLS certificate and the app allows cleartext HTTP. Also high: local SQLi in the FCM push handler (CVE-2026-111492) and unauthenticated Images.ashx profile-photo enumeration (CVE-2026-111493). Medium: plaintext credentials in SQLite/SharedPreferences (CVE-2026-111491) and embedded APK config/keys (CVE-2026-111495). Vendor has already deployed server fixes for CVE-2026-111490 and CVE-2026-111493; INCIBE says install the latest app version for the rest. Reported by Sergi García Tárraga. No known exploitation stated in the advisory.
Fixed in
Server-side fixes for CVE-2026-111490 and CVE-2026-111493 already deployed by the vendor (apply regardless of app version), Latest available MatchPoint app version for the remaining CVEs (per INCIBE)
2026-11-05: INCIBE-CERT publishes INCIBE-2026-841 coordinating disclosure of seven MatchPoint (TPC Software) flaws: three critical (CVE-2026-111489 static mobile-app credential → 'autorizado' API token; CVE-2026-111490 IDOR via actingasuser header exposing personal/banking data and account takeover; CVE-2026-111494 Android TLS TrustManager accepts any cert / allows HTTP), plus high SQLi and unauth Images.ashx photo enum and medium plaintext-credential / embedded-config issues. Server fixes for CVE-2026-111490 and CVE-2026-111493 already deployed; remaining issues need the latest app version. Reported by Sergi García Tárraga. (source)
Apache OFBiz 24.09.08 fixes 46 vulnerabilities in every earlier release, several of them critical. Unauthenticated attackers can run code on the server through login-page widget injection (CVE-2026-83542), attacker-controlled Screen definition loading (CVE-2026-68524) and a saved-view authorization bypass (CVE-2026-73578). They can also take over a full user session by replaying a captured externalLoginKey (CVE-2026-82907). On 24.09.06 and 24.09.07 deployments upgraded from older releases, a forged JWT signed with the old default key gives admin access (CVE-2026-105330). The batch also includes a password-reset account takeover, a REST auth bypass when the auth attribute is omitted, SQL injection, XXE, SSRF and many missing-authorization bugs. No exploitation has been reported, but older OFBiz bugs have been exploited in the wild.
2026-11-05: CVE records are published. CVE-2026-83542 (unauthenticated RCE via login-page widget injection) is rated critical, and CVE-2026-82907 (pre-auth, reusable externalLoginKey session takeover) is rated important. (source)
2026-11-04: Apache OFBiz announces 46 CVEs affecting all versions before 24.09.08, including several critical issues, and tells users to upgrade to 24.09.08. (source)
On Nov 6 2026 AWS published Important bulletin 2026-166-AWS for two memory-safety issues in the Babelfish TDS protocol layer used by Babelfish for Aurora PostgreSQL (SQL Server wire protocol). CVE-2026-119923: a memory-safety issue in the TDS connection-handshake handling could allow a remote, unauthenticated actor to affect the confidentiality, integrity, and availability of the database process. CVE-2026-119924: a memory-safety issue in the TDS remote-procedure-call request handling could allow a remote, authenticated actor to read adjacent process memory or cause a denial of service. AWS addressed the issues in Babelfish for PostgreSQL extension versions 4.10, 5.6 and 6.1, and lists patched Aurora PostgreSQL versions with Babelfish enabled. Workaround until upgraded: restrict network access to the TDS port (default 1433) to trusted sources using VPC security groups.
2026-11-06: AWS publishes Important bulletin 2026-166-AWS for CVE-2026-119923 (TDS connection-handshake memory-safety; remote unauthenticated actor can affect confidentiality, integrity, and availability of the database process) and CVE-2026-119924 (TDS RPC request handling memory-safety; remote authenticated actor can read adjacent process memory or cause DoS). Fixed in Babelfish extension 4.10 / 5.6 / 6.1 and listed Aurora PostgreSQL versions. Workaround: restrict TDS port 1433 via VPC security groups. (source)
On Nov 6 2026 AWS published Important bulletin 2026-173-AWS for CVE-2026-122193 (GHSA-95g5-m242-wvhr): an OS command injection issue in an example from the Trusted Remote Execution (REX) set-up documentation. The example script creates AWS Systems Manager documents Rex-RO and Rex-RW for running scripts on managed instances; due to how that example handled input parameters (including scriptArgs), a user permitted to invoke the SSM document could supply crafted input that runs unintended OS commands on the managed instance outside the REX sandbox. This is not a flaw in a shipped REX artifact — only operators who created those SSM documents by following the guide are affected. AWS removed the example from the guide. Mitigation: delete any Rex-RO / Rex-RW SSM documents created from the example in each account and Region where it was run. No workaround other than deleting the documents.
Fixed in
Example removed from REX set-up guide; delete any created Rex-RO / Rex-RW SSM documents
2026-11-06: AWS publishes Important bulletin 2026-173-AWS for CVE-2026-122193: OS command injection in REX set-up guide example SSM documents Rex-RO/Rex-RW; example removed from guide; delete created documents. (source)
Charmbracelet Wish (SSH server middleware for Go) before 2.0.5 has a path traversal in the git middleware that lets authenticated SSH users escape the configured repository directory with crafted repo paths. Fixed in v2.0.5 (commit 533db0d). CVSS 8.1 per NVD/VulnCheck.
NVD published a Chartbrew advisory cluster on 2026-11-06 for issues patched earlier in v5.2.1 and v5.2.3. Critical CVE-2026-85295 (CVSS 9.8): stock source/docker-compose installs keep the shipped CB_SECRET default, so an unauthenticated attacker forges session JWTs for any user (password/2FA bypass). Critical CVE-2026-54349 (CVSS 9.8): unauthenticated SQL injection via dashboard/chart filter variable substitution on public/embedded charts (fixed in 5.2.1). High CVE-2026-85712 (CVSS 8.8): authenticated cross-tenant project takeover via caller-controlled body.team_id. Same 5.2.3 wave also covers forgeable share tokens (CVE-2026-85708), MongoDB date-variable NoSQLi (CVE-2026-85726), root-path file deletion via SSL/SSH cleanup (CVE-2026-85736), unauthenticated BullMQ admin dashboard at /apps/queues (CVE-2026-86005), and NAT64 SSRF bypass in outbound URL guards (CVE-2026-54589, fixed in 5.2.1). Upgrade to Chartbrew 5.2.3 (at least 5.2.1 for the SQLi/SSRF subset) and rotate secrets.
2026-11-06: NVD receives CVE-2026-85295, CVE-2026-54349, CVE-2026-85712, CVE-2026-85708, CVE-2026-85726, CVE-2026-85736, CVE-2026-86005, and CVE-2026-54589 from security-advisories@github.com for the earlier Chartbrew patches. (source)
2026-09-06: GitHub Security Advisories published for the 5.2.3 wave including GHSA-qvv4-r3q6-8797 (default CB_SECRET ATO), GHSA-6gv3-8wxh-6vfq (cross-tenant takeover), GHSA-3chp-cr6f-hp63 (forgeable share tokens), GHSA-mr45-2r9x-cgwf (Mongo date NoSQLi), GHSA-p5h6-f969-jpfv (root file delete), and GHSA-w8g3-j8rf-qc5j (BullMQ exposure). (source)
2026-07-19: Chartbrew v5.2.3 security release: rejects legacy CB_SECRET session tokens, migrates share tokens to CB_ENCRYPTION_KEY, hardens tenant boundaries, protects BullMQ admin UI, and further query/path guards. (source)
Cisco published a high-severity advisory for UCS Central Software, its management platform for multiple Cisco Unified Computing System domains. CVE-2026-76506 (CVSS 7.6, CWE-22 path traversal) is insufficient validation of user-supplied input in an HTTP request to the web-based management interface. An authenticated remote attacker with valid user credentials can send a crafted request to execute arbitrary commands, write arbitrary files to the filesystem and obtain sensitive information. It affects UCS Central regardless of configuration, and there are no workarounds: upgrade release 2.1 to 2.1(2c), and migrate release 2.0 and earlier to a fixed release. Cisco PSIRT says it is not aware of public announcements or malicious use.
A flaw in APT, Debian's package manager, lets a man-in-the-middle attacker replace a package after it has been verified, resulting in arbitrary code execution as root. Per Debian's advisory DSA-6607-1, APT can merge two different package downloads after an HTTP redirect gives them the same URI, and improper file handling when resuming an HTTP download allows the swap. It was found by Max Justicz. Debian stable (trixie) is fixed in apt 3.0.4, which also addresses several out-of-bounds access issues, and Debian 12 (bookworm) is fixed in apt 2.6.2 (DLA-4880-1); Debian testing (forky) was still listed as vulnerable. Ubuntu published fixes on Nov 4 for 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS, with Ubuntu Pro fixes for older releases. The bug needs a non-zero Acquire::Retries setting, which is the default from Debian 12 and Ubuntu 22.04 on, so older releases are unaffected in a default configuration. No exploitation has been reported.
2026-11-04: Debian publishes DSA-6607-1 for apt (CVE-2026-109518): a man-in-the-middle attacker can replace a package after verification and run code as root; fixed in apt 3.0.4 for trixie. (source)
2026-11-04: The advisory reaches the Hacker News front page. (source)
2026-11-04: Ubuntu ships fixed apt for 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS (Ubuntu Pro fixes for older releases) and rates it CVSS 4.0 7.7 high; Debian's tracker lists bookworm fixed in apt 2.6.2 (DLA-4880-1), with forky still vulnerable. (source)
CVE-2026-121614 affects Docker Sandboxes 0.31.0 before 0.50.0. Host-side Git commands did not neutralize repository-controlled Git configuration. An attacker who can modify a host repository's Git config—for example through a direct-mode sandbox with the repo mounted read-write—can set core.fsmonitor or another setting that invokes an external program. A later clone-mode fetch, or from 0.39.0 an sbx kit push, can run that program on the host with the user's privileges, outside the microVM. Clone-mode's read-only host mount alone cannot poison the config. Fixed in Docker Sandboxes 0.50.0 (released Oct 26 2026; CVE published ~Nov 3). Vendor CVSS 4.0 is 7.1 (High). Upgrade to 0.50.0+; avoid read-write mounts of untrusted repos until patched.
2026-11-03: CVE-2026-121614 is published describing the Git-config sandbox escape in 0.31.0 before 0.50.0. (source)
2026-10-26: Docker Sandboxes v0.50.0 ships: host Git commands no longer run programs configured by a sandbox through the workspace repository's .git directory. (source)
A critical buffer overflow in TianoCore EDK II, the open source UEFI code most server firmware is built on, lets an unauthenticated attacker who can send ICMP error messages to a machine while it PXE-boots corrupt memory in the PXE Base Code driver (NetworkPkg/UefiPxeBcDxe) and run code in ring 0 before Secure Boot or measured boot check anything. The bug sits in the IPv4 and IPv6 ICMP error handlers, which copy messages longer than 504 bytes past a fixed field. Reliable code execution needs knowledge of the target firmware build; otherwise the boot hangs. The fix (PR #13302) was merged to EDK II master on Oct 15 2026, but no stable EDK II tag carries it yet and the advisory lists it as not patched. Fixes reach most machines only through firmware updates from server and board vendors. Machines that boot only from disk aren't affected. Until vendor firmware ships, disable PXE/network boot where you can. TianoCore rates it critical (CVSS 4.0 9.5).
Fixed in
EDK II master at fa78907 (PR #13302, no stable tag yet), Fedora edk2 20260812-6 (fix backported)
2026-10-28: Hetzner posts a status notice on CVE-2026-97631: an official patch isn't available yet, running systems aren't directly at risk, and it recommends avoiding reboots of hosts that use PXE boot until further notice while it analyzes its environment. (source)
2026-10-27: Ars Technica reports the bug affects firmware from most server vendors. The finders had planned a coordinated disclosure in January, but the public fix broke the embargo. Intel says none of its supported commercial products are known to be affected; Arm says it isn't directly applicable to its portfolio. (source)
2026-10-26: Fedora backports the fix into edk2 20260812-6 (updates-testing). Debian still lists its edk2 packages as vulnerable. (source)
INFINITT Healthcare advisory INFINITT-SA-2026-001 (Nov 5 2026) and NCSC.ch CVE records cover two issues in the ULite medical imaging universal viewer. CVE-2026-19877 (High, CVSS 3.1 7.5) lets an unauthenticated remote attacker brute-force the low-entropy password on image-share links with no attempt limiting, gaining unauthorized access to shared medical images within the link validity window on ULite 5.0.2.1_BN48_20260528 and earlier. CVE-2026-19876 (Medium, CVSS 6.1) is a pre-authentication reflected XSS on the login/SSO error page via an unsanitized request parameter. Both are fixed in ULite 5.0.2.1 BN50. INFINITT says there is no indication of exploitation and is deploying the update to customers under existing maintenance agreements; sites should schedule the BN50 update with INFINITT support.
2026-11-06: NCSC.ch publishes CVE-2026-19877 (High, CVSS 7.5): unauthenticated brute-force of low-entropy image-share link passwords on ULite <= 5.0.2.1_BN48_20260528; and CVE-2026-19876 (Medium, CVSS 6.1): pre-auth reflected XSS on the login/SSO error page. Fixed in 5.0.2.1 BN50. (source)
2026-11-05: INFINITT Healthcare publishes INFINITT-SA-2026-001: security update for ULite share-link access control weakness and reflected XSS in the web interface; fixed builds BN50 deploying under maintenance agreements; no indication of exploitation. (source)
A critical (CVSS 9.8) flaw in Rails Active Storage lets an unauthenticated attacker write arbitrary files on the server by uploading a crafted file, and, when attachments use the Disk service, read any file the app can read, including secret_key_base and credentials for other systems, which may lead to remote code execution. Active Storage put no limits on which ImageMagick coders an upload could reach, and its ImageMagick analyzer runs on attach, so simply attaching the upload is enough; the reported chain used an SVG reaching the MSL scripting coder. Apps are affected if they use ImageMagick for Active Storage (variant_processor :mini_magick, the default for load_defaults 6.1 or earlier), run a host ImageMagick policy that doesn't block those coders (Debian and Ubuntu's policies don't), and accept untrusted uploads. Fixed in activestorage 8.1.4.1 and 8.0.5.2, which ship a restrictive ImageMagick policy and need mini_magick 5.1 or later; series before 8.0 get no fix. No CVE yet; the advisory does not say whether it has been exploited.
Fixed in
activestorage 8.1.4.1, activestorage 8.0.5.2 (requires mini_magick >= 5.1 when using :mini_magick), Rails before 8.0: no fix; copy the shipped policy.xml rules (deny MSL, Ghostscript coders and the gs delegate) into the system ImageMagick policy
Latest updates (3)
2026-11-06: Socket publishes a free Certified Patch for GHSA-f3w6-w445-fwh9 as an interim remediation while teams upgrade to Rails 8.1.4.1 or 8.0.5.2; does not cover the other November 4 Rails security fixes. (source)
2026-11-04: Rails publishes GHSA-f3w6-w445-fwh9 (critical, CVSS 9.8) and releases Rails 8.1.4.1 and 8.0.5.2, which ship an ImageMagick security policy; reported via HackerOne by RyotaK (GMO Flatt Security). (source)
2026-11-04: The Hacker News reports the flaw; the same releases fix a second Active Storage issue, GHSA-v924-7rp8-4mxh (high, CVSS 8.8), and 21 security issues in total. (source)
Alpine Linux warned that sshd built without PAM can be logged into without a password. On those builds sshd checks a password by running crypt() and comparing the result to the stored password field, borrowing another account's salt when the stored field has none. musl's crypt() returns "*" as an error when the password is longer than 256 bytes, and "*" is exactly what the stored field holds for accounts with no password, so the comparison matches. An attacker who can reach the SSH port and knows the name of such an account can log in with one connection by sending a 257 to 1024 byte password, as long as the machine has at least one other account with a $5$ or $6$ hash. Affected setups are Alpine's openssh-server package (or openssh-server-pam with UsePAM no) with PasswordAuthentication yes, on every release Alpine checked from 3.16 through 3.24 and edge. OpenSSH released 10.6p2 on Nov 5 2026 to avoid the bug in sshd, and Alpine shipped fixed packages for 3.16 to 3.24 and edge. The bug was assigned CVE-2026-123158 later the same day. On Nov 6 2026 Previdian reported successful root access on an Alpine/OpenSSH honeypot within about nine hours of CVE publication (reconnaissance from 89.116.89.18), and watchTowr said it was observing botnet and crypto-miner exploitation.
2026-11-06: SecurityWeek covers OpenSSH's emergency SSHole patches (CVE-2026-123158) and quotes Damien Miller on rushing the release because AI agents have been rediscovering bugs within hours. (source)
2026-11-06: Help Net Security reports Previdian observed exploitation of CVE-2026-123158 less than nine hours after CVE publication, including confirmed successful root access on an Alpine Linux OpenSSH honeypot and reconnaissance commands from 89.116.89.18; CISA has not added the CVE to KEV. (source)
2026-11-06: watchTowr says its Intel feed is observing SSHole (CVE-2026-123158) exploitation, so far attributed to botnets and crypto miners. (source)
On October 25 the Atlantis project (the Terraform pull request automation server) released v0.49.0 and published 12 GitHub security advisories fixed in it. The worst, GHSA-6mjf-4m52-m5cq (CVSS 9.8, critical), comes from Atlantis checking only the path of a pull request's clone URL and not its host, while trusting the head repository name from the webhook body: a forged webhook can point Atlantis at an attacker's git server, pass the --allow-fork-prs=false gate and --repo-allowlist, and have Atlantis fetch and plan a Terraform tree the attacker controls. Servers without a GitHub webhook secret accept that forged webhook from anyone without authentication. Other fixes cover a Gitea dismissed-approval bypass of apply_requirements (GHSA-fm5f-jg8p-x2vw, 8.8), an allowed_workflows allow-list bypass in multi-project atlantis.yaml files (GHSA-56q6-8vmp-v2qm, 8.2), a plan-hijack apply-approval bypass (GHSA-5vwh-xc92-8h64), a pull request symlink that makes Terraform run outside the checkout (GHSA-9q39-mgw7-5789), unauthenticated lock metadata on /api/locks (GHSA-xgrg-fpp6-q6fm), timing attacks on Basic Auth and API secrets plus path traversal on /api/plan and /api/apply, an arbitrary file read via --var-file, secrets leaking into PR comments when output hiding errors, and a CSRF in the GitHub App setup callback. The advisories do not mention exploitation. v0.49.0 is a breaking release: GitHub and GHES webhooks whose clone URL host differs from --gh-hostname are now rejected, and the Docker images no longer bundle Terraform or OpenTofu. Anyone upgrading from v0.47.0 or earlier also picks up the v0.47.1 fix for CVE-2026-116676, a PR-controlled workspace name that was passed unquoted into a shell command. Upgrade to 0.49.0 and set a GitHub webhook secret.
Fixed in
Atlantis 0.49.0, Atlantis 0.47.1 for CVE-2026-116676
2026-10-25: Atlantis releases v0.49.0, a breaking release that fixes 12 security advisories, led by the critical forged-webhook fork-protection bypass GHSA-6mjf-4m52-m5cq. (source)
2026-08-25: Atlantis publishes GHSA-rjh2-4xgw-p2hj, a shell command injection through a PR-controlled Terraform workspace name, fixed in 0.47.1 and now tracked as CVE-2026-116676. (source)
Google promoted Chrome 157 to the stable channel on Nov 3 2026 (157.0.8103.38 on Linux, 157.0.8103.38/.39 on Windows and Mac) with 213 security fixes. Seven are rated critical: buffer overflows in Dawn (CVE-2026-121156, CVE-2026-121247), memory corruption in ANGLE (CVE-2026-121229), and use-after-free bugs in WebGL (CVE-2026-121246), Prerender (CVE-2026-121035), Geometry (CVE-2026-121203) and Core (CVE-2026-121126). Many of the high-severity bugs were credited to AI-assisted research from Anthropic and OpenAI Codex Security. Google has not said any are exploited. The rollout is staged over days or weeks, so update and relaunch rather than waiting.
2026-11-04: Hong Kong's GovCERT issues an alert telling users to update Chrome to 157.0.8103.38 or later, warning the flaws could allow remote code execution. (source)
2026-11-03: Chrome 157 promoted to stable with 213 security fixes, seven of them critical (Dawn, ANGLE, WebGL, Prerender, Geometry, Core); none reported exploited. (source)
A remote code execution vulnerability exists in the Field UI module in Drupal core. It isn't directly exploitable with core alone, but the Drupal Security Team says multiple serious exploit paths exist with contributed modules, at least one without authentication, and custom code may also expose it. Rated Critical (19/25). Update to Drupal 11.4.10, 11.3.19 or 10.6.19; uninstalling the core Field UI module (field_ui) mitigates it until then.
2026-10-14: Drupal Security Team publishes SA-CORE-2026-014: Critical RCE in the core Field UI module, fixed in 10.6.19, 11.3.19 and 11.4.10; uninstalling field_ui mitigates. (source)
imgproxy's ICO loader (vips/icoload.c) has three related flaws reachable with a crafted image. GHSA-hff9-5pqw-6w9f is a critical unauthenticated integer overflow: an attacker-controlled 32-bit data_size wraps when BMP_FILE_HEADER_LEN is added, so the process allocates a few bytes then writes far past the buffer — GitHub rates it CVSS 3.1 9.8 and says the heap overflow can cause denial of service or remote code execution. GHSA-mmq5-xm89-9pfg (high, CVSS 7.5) passes the same data_size to VIPS_MALLOC without a bound, so a tiny ICO can force a multi-gigabyte allocation. GHSA-494m-4556-wf5p (high, CVSS 7.5) reconstructs a BMP header from unvalidated fields and can write out of bounds, crashing the worker. Fixed in v4.0.16 (overflow + unbounded alloc) and v4.0.17 (OOB heap R/W). Also tracked as GO-2026-6897, GO-2026-6898 and GO-2026-6895.
mark3labs/mcp-go's MCPServer.HandleMessage decodes JSON-RPC with encoding/json, which matches member names case-insensitively, folds ſ (U+017F) to s and K (U+212A) to k, and keeps the last of duplicate members. A request with Method/METHOD/paramſ, or with method given twice, still runs as the named call. mcp-go does not authorize calls itself, so this matters when a gateway or proxy in front allowlists method / params.name with an exact-match parser: the proxy may not see the call the server executes. The official Model Context Protocol Go SDK had the same class of bug (CVE-2026-27896 / GHSA-wvj2-96wp-fq3f) and fixed it in 1.3.1. Reported privately to contact@mark3labs.com on 2026-08-16 with no reply, then disclosed. Affected through v1.5.0 (tested on v1.0.0-beta.1, v1.4.0 and main after v1.5.0); no fix released. Workarounds: reject messages whose member names are not exactly the defined ones or that repeat a member, or re-encode before forwarding.
Latest updates (3)
2026-11-04: golang/vulndb#6911 opened describing the mcp-go JSON-RPC case/Unicode-folding proxy-allowlist bypass; fixed in: not fixed. (source)
2026-11-04: Public disclosure filed as mark3labs/mcp-go#1164 after private report and follow-up went unanswered. (source)
2026-08-16: Issue reported privately to contact@mark3labs.com; no reply (per public disclosure). (source)
nodejs/undici shipped coordinated security releases 7.30.2 and 8.12.4 on Nov 5 2026 fixing six advisories. High GHSA-mqg3-3v4r-cm32 / CVE-2026-116592 lets an originless Agent with compose(redirect(), cache()) and a shared cache poison or disclose across users because only the final redirect hop was checked, so intermediate hops could bypass the earlier CVE-2026-109829 fix (affected >=7.30.1 <7.30.2 and >=8.12.2 <8.12.4). Five Medium issues in the same release cover same-origin redirect cache disclosure (GHSA-7xg3-fphp-28hg / CVE-2026-120474), cross-origin redirect revalidation disclosure (GHSA-5rm8-gv32-r954 / CVE-2026-116630), array-of-tuples headers bypassing redirect credential stripping (GHSA-9v6h-8rgp-m69f / CVE-2026-120415), unhandled exception DoS during cache-interceptor response replay (GHSA-3g9m-rv3r-w5w2 / CVE-2026-120222), and Subresource Integrity bypass when integrity metadata uses non-space ASCII whitespace such as a tab (GHSA-r4pc-4jcp-7pqc / CVE-2026-120423). Upgrade to undici 7.30.2 or 8.12.4.
Puppet by Perforce and the OpenVox fork released coordinated fixes on Nov 3 2026 for two critical bugs found by Neodyme that affect all known Puppet and OpenVox versions, going back at least to open-source Puppet 6.24.0 from July 2021. CVE-2026-115731 lets any client holding a CA-signed agent certificate run arbitrary code on the Puppet/OpenVox server as its service user by submitting a report with a crafted rich-data event, because the event is deserialized into Ruby code. CVE-2026-115732 is a flaw in trapperkeeper-authorization's certificate-name matching that lets a certificate such as evil.target.example.com be authorized as target.example.com, exposing that node's catalog and secrets, and in Puppet Enterprise it can lead to CA administration and commands on managed nodes. Where the CA autosigns certificate requests without strong verification, an unauthenticated attacker can get the certificate both bugs need. Neodyme's writeup shows the server RCE being used to steal the CA signing key and run commands as root on managed agents. Upgrade OpenVox to openvox-agent 8.32.0 or 9.3.0, openvox-server 8.18.0 or 9.2.0 and openvoxdb 8.18.0 or 9.2.0, or Puppet Enterprise to 2023.8.13, 2025.12.1 or 2026.0.1 (Puppet Core 9.1.3, Puppet Server 9.0.24.1), then restart the server. OpenVox says open-source Puppet will not get security updates and recommends migrating.
2026-11-03: OpenVox publishes critical advisories GHSA-ffr6-rwpm-p5wq (server RCE via report event deserialization) and GHSA-q4hm-33rc-572g (client impersonation via flawed hostname check) and releases fixed agent, server and OpenVoxDB versions, coordinated with Puppet by Perforce. (source)
2026-11-03: CVE-2026-115731 and CVE-2026-115732 are published; Puppet ships Puppet Server 9.0.24.1 with Puppet Core 9.1.3 patched for both. (source)
2026-11-03: Neodyme publishes its technical writeup, showing the RCE works back to Puppet 6.24.0 and can be chained to steal the CA key and run commands as root on managed agents in Puppet Enterprise. (source)
Paulos Yibelo / pwn.ai found a Critical Linux networking flaw (CVE-2026-99999, CVSS 9.3) during Vercel’s $1M Sandbox challenge. Guest-controlled checksum metadata can rewrite an IPv4 header after validation, enabling host-memory disclosure and, in lab conditions, guest-to-host code execution on KVM/Firecracker. Upstream fix merged Oct 2026; host kernels need patch + reboot. Affects multi-tenant VPS / sandbox providers more than end-user desktops. Fly.io published an Oct 16 2026 postmortem of a ~10-hour fleet-wide host reboot after the CVE, saying customer data exposure was unlikely but advising rotation of credentials sent over HTTP or unencrypted 6PN between Oct 15 and 17.
Fixed in
Upstream commit 6785011f8b16 and matching stable backports; vendor kernels as listed by distros
2026-10-16: Fly.io begins an emergency fleet-wide host reboot for CVE-2026-99999 (PwnEscape), completing the patched-kernel rollout in about 10 hours; later postmortem says customer data exposure was unlikely but advises rotating credentials sent over HTTP or unencrypted 6PN Oct 15–17. (source)
SonicWall disclosed two flaws in its end-of-life Global Management System (GMS) 9.5.2 and earlier and said no security update will be released. CVE-2026-109593 lets an unauthenticated attacker with network access read internal GMS files and expose sensitive information (CVSS 9.1 from CISA's ADP). CVE-2026-109594 is a post-authentication SQL injection that can let a high-privileged attacker access or modify data in the GMS database (CVSS 6.8). The flaws were reported by Pentest-Tools researchers. SonicWall urges customers to move to Network Security Manager (NSM); until then, keep GMS off untrusted networks.
2026-11-04: BleepingComputer reports SonicWall's warning about the unpatched GMS flaws. (source)
2026-11-03: SonicWall publishes SNWLID-2026-0019 for CVE-2026-109593 and CVE-2026-109594 in EOL GMS and says no remediation will be released; it recommends upgrading to NSM. (source)
WordPress released 7.1.4 on Oct 28 2026 as a security release and recommends updating sites immediately. It fixes a weakness in the WordPress upgrade process that can lead to remote code execution during the upgrade window (reported by Umut Bayram), a long list of stored XSS issues (crafted block markup, Privacy Data Removal Requests, the Interactivity API, Customizer selective refresh, the Categories, Playlist, image and comments-pagination blocks, and specially crafted user logins), a stored denial of service in the Interactivity API, unpublished Customizer changesets being discoverable by unauthenticated users, and Notes being readable by privileged users who can't edit the post. It also updates the bundled root certificates because of the eMudhra revocation. Sites with automatic background updates get it automatically; the fixes are being backported to every branch still eligible for security fixes (back to 4.7), and those backports ship as they become ready. WordPress 7.2 Beta 3 has the same fixes. Wordfence rates the upgrade-window RCE CVSS 8.1 (unauthenticated, high complexity: WordPress 4.7 to 7.1.3 unpack full-package updates into a predictable, web-reachable folder under wp-content/upgrade, and an attacker who requests the staged installer in the seconds-long window can reach PHP code execution). Wordfence says attackers began trying to exploit it within minutes of its firewall rule going live on Oct 28 and logged more than 18,500 requests to staged setup-config.php paths in 21 hours; it reports attempts, not confirmed compromises.
Fixed in
7.1.4, 7.0.8, 6.9.11, backports down to 4.7.39, 7.2 Beta 3
2026-11-06: Wordfence publishes that attackers are actively probing for the WordPress upgrade-window RCE (CVE-2026-119977); discussed on Hacker News. Sites should stay on patched branches and keep wp-content/upgrade non-web-executable during upgrades. (source)
2026-11-06: The Hacker News reports Picus Security researcher Umut Bayram warning that installing the 7.1.4 (or branch) fix can still expose some sites one last time: the update that installs the fix unpacks using the old updater, so complete-package upgrades on 5.9+ can leave a predictable installer under wp-content/upgrade during the window. He advises denying web access to wp-content/upgrade before updating (or doing a manual out-of-web-root update); partial same-branch packages may not include installer files, but WordPress can fall back to a complete package. (source)
2026-11-03: CISA adds CVE-2026-119977 (WordPress Core TOCTOU race during full-package upgrades) to the Known Exploited Vulnerabilities catalog; federal agencies have until Nov 6 2026 to remediate. (source)
ZITADEL published three account takeover advisories for its Login V2 UI, with CVE records on Oct 29 2026. CVE-2026-119127 (CVSS 4.0 8.6) is a host header injection: unauthenticated attackers who know a victim's login name can poison password-reset, invite and email-verification links via the x-zitadel-public-host, x-zitadel-forward-host or x-forwarded-host headers, harvest the single-use codes and take over accounts, including instance administrators. CVE-2026-119128 (CVSS 4.0 9.1) lets unauthenticated attackers compute a valid verificationCheck cookie from the user ID and browser fingerprint and set the first credential (password, passkey or linked identity provider) of users that have no authentication method yet. CVE-2026-119129 (CVSS 4.0 8.6) is missing authorization in OAuth 2.0 device authorization: a signed-in user who opens a link carrying the attacker's user code hands over their tokens, and project access settings can be bypassed via the OIDC device authorization API. 4.0.0 before 4.19.5 is affected by all three; 3.0.0 through 3.4.15 is also affected by the device authorization bug.
Better Auth, a popular TypeScript authentication library, published a critical advisory on Nov 3 2026 for its expo() server plugin. The plugin's public /expo-authorization-proxy endpoint signed a caller-supplied state value with the application secret without checking that the server had issued it. Because Better Auth uses the same secret for email verification links and the session cookie cache, an unauthenticated attacker who knows a user's email address can sign in as that user and change the account's email, and with the cookie cache enabled, an attacker who knows a user ID can act as that user. The same endpoint was also an open redirect, and wildcard trustedOrigins entries could match URLs outside the intended scheme, host or path. You are affected if your server registers expo() from @better-auth/expo 1.4.0-beta.6 or later. Upgrade both @better-auth/expo and better-auth to 1.7.16 (or 1.8.0-beta.5), then rotate the application secret, because signatures issued before the fix stay valid until it changes.
2026-11-04: CVE-2026-121802 is published and GitHub's advisory database lists it as critical (CVSS 9.1). (source)
2026-11-03: Better Auth publishes GHSA-4wq4-2ppv-q3hg and releases 1.7.16 and 1.8.0-beta.5, fixing the Expo authorization proxy signing, an open redirect and loose wildcard trusted-origin matching; it tells users to rotate the application secret after upgrading. (source)
Fortinet FortiMail CVE-2026-104286 (CVSS 9.8) is an unauthenticated arbitrary file write via path traversal / null-byte issues in Identity-Based Encryption web flows. CISA confirmed active exploitation and ordered federal mitigation; Fortinet published FG-IR-26-175 with patches and interim mitigations (disable IBE / restrict admin/webmail).
Embedthis GoAhead, the embedded web server behind device-management pages on many IoT, firewall and OT products, fixed eleven advisories in 6.1.1. The critical ones: a Basic and form-auth bypass for users with BF1 (Blowfish) stored hashes where any password works (6.1.0, CVE-2026-115888), OpenSSL builds that load a CRL but never enforce it so revoked mTLS client certificates are still accepted (3.4.5 to 6.1.0, CVE-2026-115881), and Windows CGI command injection through .bat/.cmd scripts run via cmd.exe. Others include mTLS chain-depth bypass on LibreSSL legacy-verifier builds (CVE-2026-115884), httpoxy-style CGI HTTP_PROXY injection (CVE-2026-115882), CGI ISINDEX option injection (CVE-2026-115880), a 1-byte DH modulus on Mbed TLS builds that makes TLS 1.2 DHE_RSA sessions decryptable, request smuggling, and session fixation. The advisories went out Oct 12; FoxIO's Oct 26 write-up on the three TLS bugs drew wide attention. Upgrade to 6.1.1; devices only get the fix when their manufacturer ships new firmware.
2026-10-28: SecurityWeek covers FoxIO's findings; FoxIO has released proof-of-concept code and fingerprints for spotting internet-facing GoAhead servers and their TLS library, and stresses that device fixes depend on each manufacturer. (source)
2026-10-26: FoxIO publishes 'Three TLS Bugs in GoAhead' (CRL bypass, LibreSSL chain-depth bypass, Mbed TLS 1-byte DH modulus) and warns that hundreds of millions of devices embed GoAhead and rarely get updated. (source)
2026-10-12: Embedthis publishes eleven GoAhead security advisories and the v6.1.1 release (shipped to device builders Aug 2), including critical BF1 auth bypass, OpenSSL CRL non-enforcement and Windows CGI command injection. (source)
iTerm2, the popular macOS terminal, has an argument injection bug in its x-man-page: URL handler in versions before 3.7.7beta2. Per the CVE record, percent-encoded NUL characters survive iTerm2s input sanitization and are later turned into whitespace, so a crafted link can inject extra arguments into /usr/bin/man, including -P to pick an attacker-controlled pager command that runs with the users privileges. The victim has to open the crafted URL in iTerm2, for example by clicking it in a browser where iTerm2 handles the x-man-page scheme (a browser or macOS confirmation may appear) or in terminal output. The record notes it exists because of an incomplete fix for CVE-2023-46321. The fix landed in 3.7.7beta2, and stable iTerm2 3.7.7 (built Nov 3 2026) now checks man section and page names against a character allowlist; the release notes credit vin01 for finding it. The CVE record rates it CVSS 4.0 8.7 (high). No exploitation has been reported.
2026-11-05: CVE-2026-123014 is published: percent-encoded NUL characters let a crafted x-man-page: URL inject arguments such as -P into /usr/bin/man and run arbitrary commands, an incomplete fix for CVE-2023-46321; CVSS 4.0 8.7. (source)
2026-11-03: iTerm2 3.7.7 ships with a hardened x-man-page: handler: man section and page names are checked against an allowlist and URLs with disallowed characters are rejected; the release notes credit vin01 for finding the bug. (source)
Laravel's built-in TokenGuard, when configured as a standard token-based API guard, can be bypassed to log in as an arbitrary existing user without their API token. On some database configurations (MySQL/MariaDB), a crafted non-string credential is mishandled during the lookup so the query matches an unintended user instead of failing. An unauthenticated attacker can take over accounts on any route protected by that guard. Upgrade laravel/framework to 12.68.0 or 13.29.0. GitHub rates it critical (CVSS 4.0 score 9.2).
Sansec reports a criminal group that has injected a JavaScript loader into the cms_block table of 953 online stores since July 2025, mostly Magento. The newest loader domain, deepveindrilling.com (registered Oct 6, 2026), was found on 83 stores, and since Oct 23 it fingerprints visitors so scanners get nothing. Sansec ties initial access to PolyShell (CVE-2026-48356, fixed in Adobe APSB26-73) and SessionReaper (CVE-2025-54236, APSB25-88), plus rogue admin accounts on fully patched stores. Store owners should patch, audit cms_block and cms_page, remove rogue admins and rotate credentials.
Fixed in
APSB26-73 (2.4.x-2026-jul security releases) for CVE-2026-48356, APSB25-88 for CVE-2025-54236
2026-10-27: CISA adds CVE-2026-48356 (Adobe Commerce and Magento unrestricted file upload, PolyShell) to its Known Exploited Vulnerabilities catalog based on evidence of active exploitation. (source)
2026-10-24: Sansec publishes its research: 953 stores across five loader domains since July 2025, 83 on deepveindrilling.com (60 of them earlier victims). (source)
2026-10-23: Operator rewrites the blocks with a fingerprinting loader that hides from automated browsers; 9 more stores infected, including a fully patched 2.4.7-p10 store with a rogue admin account. (source)
Self-managed Airbyte before 2.2.0 let Connector Builder / Manifest Server load unintended Python classes from a declarative manifest custom component, even when AIRBYTE_ENABLE_UNSAFE_CODE was off, so a user who could submit a test-read manifest could run commands inside those containers. On Airbyte 2.x that needs Workspace Reader or Organization Reader (or higher); on Airbyte 1.x with the legacy Helm chart the Connector Builder ignored global.auth.enabled, so anyone who could reach that service could exploit it unauthenticated. Successful exploitation may expose credentials and secrets in the container and reach internal services. Fixed in Airbyte 2.2.0 (manifest-server 7.23.7); Airbyte 1.x will not get a fix and should upgrade to 2.2.0+. Airbyte Cloud is not affected. JVN#12040144 (published Nov 4 2026) states the flaw has been confirmed exploited in the wild. Workarounds until you upgrade: restrict network access to Connector Builder / Manifest Server to the Airbyte server only, and limit Reader roles to trusted users.
2026-11-04: JVN#12040144 publishes the Airbyte arbitrary code execution issue and states the vulnerability has been confirmed to be exploited in the wild; upgrade self-managed deployments to the latest version. (source)
2026-10-17: Airbyte publishes GHSA-g35w-6r6v-h4r7 describing Connector Builder / Manifest Server arbitrary command execution via unrestricted custom-component class loading, fixed in 2.2.0; Airbyte 1.x will not receive a fix. (source)
2026-08-10: Airbyte 2.2.0 is released for self-managed deployments, shipping manifest-server 7.23.7 and rejecting Connector Builder custom components unless AIRBYTE_ENABLE_UNSAFE_CODE=true. (source)
Two flaws in the Xen hypervisor's grant copy operation let a malicious guest VM read and write arbitrary memory belonging to other domains, including dom0, breaking VM isolation on the host. Xen caches already-validated data during batches of grant copies on the same page, but re-validated it incorrectly: frame numbers and grant references could be mixed up (CVE-2026-102703), and the check limiting copy-by-frame-number to the caller's own memory was misplaced (CVE-2026-102704). Every Xen version from 4.6 onward is vulnerable and there is no mitigation. The Xen Project published patches for xen-unstable through 4.17.x on Nov 3 2026; XCP-ng 8.3 and Qubes OS 4.3 shipped fixed packages that need a host or dom0 reboot, while Debian stable releases were still listed as vulnerable on Nov 4. Found by Anthropic using Claude and validated by Ada Logics; no exploitation has been reported.
Fixed in
Xen xen-unstable to 4.19.x: xsa523-1/2 patches, Xen 4.18.x to 4.17.x: xsa523-4.18-1/2 patches, XCP-ng 8.3: xen-4.17.7-4.2.xcpng8.3 (reboot required), Qubes OS 4.3: Xen 4.19.6-3 in dom0 (security-testing first; restart required)
2026-11-03: Xen Project publishes XSA-523 (CVE-2026-102703, CVE-2026-102704) with patches for xen-unstable through Xen 4.17.x; no known mitigation. (source)
2026-11-03: XCP-ng releases xen-4.17.7-4.2.xcpng8.3 and Qubes OS publishes fixed Xen 4.19.6-3 packages for Qubes 4.3; both require a host or dom0 reboot. (source)
On Nov 6 2026 NVD published three Gen Digital (security@nortonlifelock.com) advisories affecting Avast, AVG and Norton Windows products before 26.7. CVE-2026-80301: the Avast sandbox virtualizes filesystem/registry but does not adequately restrict Task Scheduler COM, so a local low-privileged process inside the sandbox can schedule host tasks and escape to elevated host code execution. CVE-2026-80302: insufficient isolation in sandbox file virtualization lets a sandboxed process write arbitrary files to protected host locations and achieve host code execution. CVE-2026-80303: an integer underflow in the WFP stream parser can crash the system (DoS), triggerable remotely via filtered network traffic or locally. Update Avast/AVG/Norton to 26.7 or later.
2026-11-06: NVD publishes CVE-2026-80301 (Avast/AVG/Norton sandbox escape via Task Scheduler COM), CVE-2026-80302 (sandbox file-virtualization arbitrary write to host), and CVE-2026-80303 (WFP stream-parser integer underflow DoS), fixed in version 26.7+. Gen Digital is the CVE sourceIdentifier. (source)
On Oct 21 2026 the Nuxt Content maintainers published three High advisories for the default unauthenticated POST /__nuxt_content/:collection/query endpoint in nuxt/content v3. CVE-2026-102650 (GHSA-xxrh-5hgg-gj4h): assertSafeQuery blocked only a small set of SQL keywords and did not reject expensive SQLite functions (randomblob/zeroblob/hex/length), so an unauthenticated attacker could force large allocations and block the Node event loop (DoS). GHSA-p7p3-px4q-v2rr: quote-escape and FROM-matching bugs in assertSafeQuery enabled unauthenticated boolean-blind SQL injection to read any table the DB user can see. GHSA-wjh8-qcrm-wf29: improper validation allowed unauthenticated cross-table data reads. Affected: nuxt/content >=3.0.0 <3.15.2 (fixed DoS/SQLi class in 3.15.2); further hardening in 3.16.1/3.16.2. Upgrade to >=3.16.2. Fully static prerendered deployments without the API route are not affected. Workaround: block POST /__nuxt_content/*/query at the proxy/WAF or prerender so the endpoint is not deployed.
Fixed in
3.15.2, 3.16.2 (recommended; further assertSafeQuery hardening)
Four Plex Media Server flaws (CVE-2026-96652/96654/96655/96656), together called Plex2Shell, chain to unauthenticated admin-token theft and code execution. Researcher Zach Main published details Oct 16 and a PoC shortly after; exploitation of internet-facing servers (cryptominers + residential proxies) began by Oct 17. Fixed in 1.43.3.10861 (released earlier in August); CISA added the chain to KEV with a federal deadline of Oct 23.
2026-11-06: QNAP publishes a security notice confirming reports that Plex Media Server on customer NAS devices was compromised via Plex2Shell; PSIRT says the flaws are only in Plex (QTS/QuTS hero unaffected). Urges App Center update to Plex 1.43.3.10861+, treating internet-exposed vulnerable installs as potentially compromised (clean reinstall + reset Plex/NAS credentials; patch alone will not remove payloads), and disabling Remote Access / port 32400 unless using a VPN. (source)
2026-10-21: CISA KEV warning; patch-by Oct 23 for federal agencies.
2026-10-20: CISA adds CVE-2026-96652, -96654, -96655, -96656 to KEV (federal due dates Oct 23 for -96654/-96656, Nov 3 for -96652/-96655). (source)
On Nov 4 2026 Symfony disclosed two high-impact Serializer file-read bugs fixed in symfony/serializer 5.4.56 / 6.4.50 / 7.4.23 / 8.1.11. CVE-2026-118515: when deserializing untrusted data into a DTO with an UploadedFile (or other SplFileInfo subclass) property—common with #[MapRequestPayload]—ObjectNormalizer could instantiate UploadedFile from attacker-controlled path/originalName/test fields, so the app treats any PHP-readable server file as an upload (read, move via rename when test:true, or path existence). CVE-2026-121623 (GHSA-pxj9-jh84-vhm5): DataUriNormalizer accepted case-insensitive DATA: schemes that PHP opens as relative local paths, so denormalizing to SplFileObject/File/SplFileInfo could read arbitrary files (e.g. DATA:,/../../../../etc/hostname). FrameworkBundle registers DataUriNormalizer by default. Same-day Symfony published six additional Serializer/security advisories; upgrade Serializer (or the framework release that pulls these versions) on every maintained branch.
2026-11-04: Symfony publishes CVE-2026-118515: Serializer DataUriNormalizer / ObjectNormalizer path lets clients build UploadedFile objects pointing at arbitrary server files when deserializing untrusted data (e.g. MapRequestPayload DTOs). (source)
2026-11-04: Symfony publishes GHSA-pxj9-jh84-vhm5 (CVE-2026-121623): DataUriNormalizer accepts non-lowercase DATA: schemes that PHP opens as local paths, enabling arbitrary server file reads via SplFileInfo/File/SplFileObject denormalization. (source)
2026-11-04: Both Serializer file-read issues fixed in symfony/serializer 5.4.56, 6.4.50, 7.4.23 and 8.1.11 as part of an eight-advisory security release day. (source)
Attackers stole Bitcoin and Litecoin from hot wallets on self-hosted BTCPay Server instances running 2.4.1 (released July 23, 2026) or earlier. BTCPay says they used a different method to exploit the vulnerability fixed in 2.4.2 (August 7) and logged in as an administrator on hit servers. It has seen no impact on servers already on 2.4.2 or later and no credible drain reports on the latest 2.4.7. Bitquery counted about $1.62M (18.38 BTC and 3,405 LTC) across 682 sweeps. Operators on 2.4.1 or earlier should sweep remaining hot-wallet funds to a new wallet with a new seed, move to a fresh server on the latest release, and rotate every credential the old server could reach, even if no theft was noticed. Wallets with spending keys held off the server were not affected.
2026-11-05: VulnCheck publishes CVE-2026-119757 (CVSS 3.1 9.8 / CVSS 4.0 9.3) for the issue fixed in 2.4.2: unauthenticated remote retrieval of LND .macaroon credential files, giving full control of the Lightning node and its funds. (source)
2026-11-03: Bitquery counts about $1.62M (18.38 BTC and 3,405 LTC) stolen across 682 sweeps, 87% of it on November 1, as reported by The Hacker News. (source)
2026-11-02: BTCPay publishes its investigation: attacks targeted 2.4.1 and earlier; operators on those versions should move to a fresh server with a new wallet and rotate credentials. (source)
