# Threat Watch by Helix

> Live security incidents: actively exploited vulnerabilities, breaches and supply-chain attacks — patch status, fixed versions and what to do, curated by Helix Cyber.

All endpoints are public JSON/XML/text with CORS enabled; no auth. Poll changes.json at most hourly with If-None-Match (every response carries an ETag).

## Categories

Every incident has exactly one `category`.
- Vulnerabilities (`patch`): 1785 incidents, 39 live. Flaws in software you may run — which versions are affected, the fixed release, and what to do first. Page https://helix.ml/threat-watch?c=patch · RSS https://helix.ml/threat-watch/c/patch/feed.xml · JSON Feed https://helix.ml/threat-watch/c/patch/feed.json · changes https://helix.ml/threat-watch/c/patch/changes.json · llms.txt https://helix.ml/threat-watch/c/patch/llms.txt
- Breaches (`breach`): 987 incidents, 5 live. Attacks on companies and services. Nothing to patch on your side; rotate credentials and watch for follow-on phishing if you are a customer. Page https://helix.ml/threat-watch?c=breach · RSS https://helix.ml/threat-watch/c/breach/feed.xml · JSON Feed https://helix.ml/threat-watch/c/breach/feed.json · changes https://helix.ml/threat-watch/c/breach/changes.json · llms.txt https://helix.ml/threat-watch/c/breach/llms.txt
- Supply chain (`supply-chain`): 7 incidents, 4 live. Compromised packages, releases, build pipelines and certificates. Check what you depend on and what you trust. Page https://helix.ml/threat-watch?c=supply-chain · RSS https://helix.ml/threat-watch/c/supply-chain/feed.xml · JSON Feed https://helix.ml/threat-watch/c/supply-chain/feed.json · changes https://helix.ml/threat-watch/c/supply-chain/changes.json · llms.txt https://helix.ml/threat-watch/c/supply-chain/llms.txt

## Data

- All incidents: https://helix.ml/threat-watch/incidents.json
- One incident: https://helix.ml/threat-watch/i/<slug>.json (timeline, sources, `agentBrief` markdown)
- Update stream: https://helix.ml/threat-watch/changes.json
- Fields: severity (critical|high|medium|low|unknown), patchStatus (patched|partial|unpatched|no-fix-needed|unknown), status (live|closed), exploited, stacks, tags, cveIds, affectedVersions, fixedVersions, actions.
- Incidents marked `auto: true` were generated from an authoritative catalog (CISA KEV, Have I Been Pwned) and not yet reviewed by an editor.

## Use with your AI

Poll changes.json hourly with ETag; for each new change, fetch the incident JSON, compare `stacks`, `product`, `affectedVersions` and `cveIds` against the systems and dependencies you manage, and alert only when one matches. Follow `actions`.

## Live incidents (48)

### [critical] PHP (PHP2Shell): Two critical RCE flaws in PHP under active exploitation (CVE-2026-109618, CVE-2026-109619)
https://helix.ml/threat-watch/i/php-php2shell-two-critical-rce-flaws-in-php-under-active-exploitation-cve-2026-109618-cve-2026-109619 · Vulnerabilities · partial · since 2026-10-21 · CVE-2026-109618, CVE-2026-109619, CVE-2026-115560
On 2026-10-21 the PHP Foundation released emergency updates for two critical RCE vulnerabilities, CVE-2026-109618 (RCE via OOM corruption) and CVE-2026-109619 (RCE via stale global state), collectively tracked as PHP2Shell (GHSA-w8hw-w9fx-j79w, GHSA-6wmf-4rv5-p3rp). Attacks against the flaws are ongoing; Wordfence, which protects over 5 million WordPress sites, reports no confirmed compromises yet, suggesting complex exploitation. Cisco issued a Critical advisory listing affected products (e.g., Ultra-Reliable Wireless Backhaul, Expressway, Duo Access Gateway) with fixes pending or scheduled (e.g., URWB 27.1.1 in Feb 2027, Expressway 15.5.21), workarounds in bug trackers, and many products confirmed not vulnerable. Community backported patches exist for EOL PHP 5.4-5.6. All organisations running PHP should patch immediately.
Fixed: PHP security release of 2026-10-21 (per PHP Foundation); Cisco URWB 27.1.1 (Feb 2027); Expressway 15.5.21 (TBD); Duo Access Gateway 3.2.0
Do: Update PHP to the patched releases published by the PHP Foundation on 2026-10-21; if patching is delayed, apply mitigations/workarounds and restrict exposure of PHP-facing services; Check vendor advisories for embedded PHP (Cisco bug IDs CSCwx37073, CSCwx37062; Splunk advisory) and schedule the vendor fixed releases; If running EOL PHP 5.4-5.6, apply the community backported patch or migrate to a supported PHP version; Monitor logs for exploitation attempts and confirm no signs of compromise; continue monitoring as attack activity is ongoing

### [critical] Cisco: Snort 3 security hardening release fixes out-of-bounds write, incorrect calculation, privilege management and DoS flaws across multiple products (CVE-2026-20043, CVE-2026-20236, CVE-2026-20291, CVE-2026-20356)
https://helix.ml/threat-watch/i/cisco-snort-3-security-hardening-release-fixes-out-of-bounds-write-incorrect-calculation-privilege-management-and-dos-fl · Vulnerabilities · patched · since 2026-10-21 · CVE-2026-20011, CVE-2026-20043, CVE-2026-20218, CVE-2026-20221, CVE-2026-20236, CVE-2026-20291, CVE-2026-20356, CVE-2026-76445, CVE-2026-76524
Cisco's Snort 3 engineering team completed an internal security review and released hardening updates addressing multiple internally discovered vulnerabilities, grouped by CWE with one CVE per class: CVE-2026-20043 (out-of-bounds write, CWE-787), CVE-2026-20236 (incorrect calculation, CWE-682), CVE-2026-20291 (improper privilege management, CWE-269) and CVE-2026-20356 (uncontrolled resource consumption, CWE-400), with a maximum CVSS of 9.0. Affected products include Cisco Cloud-delivered Firewall, Cyber Vision, Meraki MX, Secure Access, Secure Firewall Threat Defense and UTD on IOS XE; Snort 2 is not affected. The flaws were found in internal testing and are not known to be exploited. Snort 3.12.4.0, Cyber Vision 5.6.0 and various FTD releases contain fixes; CDFW, CSA and Meraki instances were updated automatically on 2026-10-21. No workarounds exist.
Fixed: Snort 3.12.4.0; Cyber Vision 5.6.0; FTD 7.0.10 / 7.2.12 / 7.4.8 / 7.6.6 / 7.7.13 / 10.0.2 / 10.1.0
Do: Upgrade Open Source Snort 3 to 3.12.4.0 or later; Upgrade Cisco Cyber Vision to 5.6.0 (or migrate from older releases); Upgrade Cisco Secure FTD to the first fixed release for your train (7.0.10, 7.2.12, 7.4.8, 7.6.6, 7.7.13, 10.0.2 or 10.1.0); Update UTD on Cisco IOS XE per the advisory's fixed release table; Verify CDFW, CSA and Meraki MX devices are online so automatic Snort 3 package updates have applied

### [critical] Cisco Expressway Series: unauthenticated root RCE via static credentials plus hardening-release batch (CVE-2026-76466)
https://helix.ml/threat-watch/i/cisco-expressway-series-unauthenticated-root-rce-via-static-credentials-plus-hardening-release-batch-cve-2026-76466 · Vulnerabilities · patched · since 2026-10-21 · CVE-2026-76435, CVE-2026-76466, CVE-2026-76490, CVE-2026-76491, CVE-2026-76492, CVE-2026-76493, CVE-2026-76494, CVE-2026-76495, CVE-2026-76496, CVE-2026-76497
Cisco published advisories on 2026-10-21 for Cisco Expressway Series (Expressway-C/E). CVE-2026-76466 (CVSS 9.8, CWE-798) is a critical unauthenticated remote RCE: use of persistent cookies plus insufficient client-certificate validation in clustering lets an attacker with network access connect to the database service and invoke RPC commands to execute arbitrary OS commands as root. It affects devices running X15.5.3 or earlier when configured in a cluster; no workarounds exist. A companion hardening advisory (cisco-sa-exwy-hardening-FhcqBVcs, max CVSS 8.6) fixes eight internally discovered issues (CVE-2026-76490 through -76497) covering out-of-bounds write, reachable assertions, null derefs, code injection, link following, insecure temp files and permission flaws, found partly using frontier AI models. Neither is known to be exploited. Fixed in X15.5.20; X14 and earlier must migrate.
Fixed: X15.5.20
Do: Upgrade clustered Expressway-C/E devices to X15.5.20 or later immediately, prioritising internet-facing Expressway-E; Migrate devices on X14 or earlier to a fixed release; Restrict network access to the database service and clustering ports (firewall/ACL) as interim mitigation until patched; Audit cluster configurations and TLS Verify Mode settings; review logs for suspicious RPC connections to the database service; Apply the October 2026 hardening release fixes to all Expressway deployments regardless of clustering configuration

### [critical] npm typosquat cluster (appit-* / ionic-insta-search): malicious packages flagged as malware
https://helix.ml/threat-watch/i/npm-typosquat-cluster-appit-ionic-insta-search-malicious-packages-flagged-as-malware · Supply chain · no-fix-needed · since 2026-10-25
On 2026-10-25 GitHub published four malware advisories (GHSA-fr38-45mf-vcqf, GHSA-5pw8-3xv5-6cmg, GHSA-4fw4-xm5r-mh69, GHSA-9w8h-674f-4x2j) covering npm packages appit-cordova-plugin-ionic, cordova-plugin-geofence-appit, ionic-insta-search and appit-cordova-admob. All versions (>= 0) are affected, CWE-506 embedded malicious code, no patched versions exist. The advisories state any machine with these packages installed or running should be considered fully compromised, implying credential/key theft and remote control by an outside party. The names mimic legitimate Cordova/Ionic plugins, suggesting a typosquatting or account-compromise campaign targeting Ionic/Cordova developers. No exploitation details or fixed versions are available; removal alone may not eliminate the compromise.
Do: Rotate all secrets, keys, tokens and credentials stored on or accessible from any machine where these packages were installed, using a clean machine; Remove the packages from all projects and lockfiles and rebuild from a clean environment; Audit build machines and developer workstations for persistence, unexpected processes and network connections; Check CI/CD pipelines and published app artifacts for inclusion of these packages and re-sign/rebuild affected apps; Block these package names in npm dependency policies and review dependency trees for similar typosquats

### [critical] Cisco Unified Communications Products: October 2026 hardening release fixes multiple vulnerabilities across voice/collaboration suite (CVE-2026-76473 to CVE-2026-76481)
https://helix.ml/threat-watch/i/cisco-unified-communications-products-october-2026-hardening-release-fixes-multiple-vulnerabilities-across-voice-collabo · Vulnerabilities · patched · since 2026-10-21 · CVE-2026-76473, CVE-2026-76474, CVE-2026-76475, CVE-2026-76476, CVE-2026-76477, CVE-2026-76478, CVE-2026-76479, CVE-2026-76481, CVE-2026-76487
Cisco published a critical hardening release on 2026-10-21 addressing multiple internally discovered vulnerabilities across Emergency Responder, Prime Collaboration Deployment, Unified CM, Unified CM IM&P, Unified CM SME, and Unity Connection. Issues are grouped by CWE into eight CVEs (CVE-2026-76473 through CVE-2026-76481) covering injection (CWE-74, max 9.8), improper authentication (CWE-287, 9.8), XSS (9.3), input validation, SQL injection, access control (all 8.8), path traversal (7.8), and exceptional-condition handling (7.5). Vulnerabilities affect the products regardless of configuration, were found during internal testing including use of frontier AI models, and are not known to be exploited. No workarounds exist; fixed software is available — release 15SU5, while release 14 users must migrate to a fixed release.
Fixed: 15SU5 (Release 14: migrate to a fixed release)
Do: Upgrade Unified CM, Unified CM IM&P, Unified CM SME, Unity Connection, Emergency Responder, and Prime Collaboration Deployment to the first fixed releases (15SU5 for release 15; migrate off release 14); Prioritise internet-exposed Unified CM and Unity Connection instances given 9.8 unauthenticated network-attack vectors; Check for follow-up Cisco advisories detailing individual vulnerabilities and apply Snort rules 67356/67358 for detection; Since no workarounds exist, restrict network access to management interfaces until patching is complete

### [critical] Cisco Secure Email Gateway Relative Path Traversal Vulnerability (CVE-2026-76519)
https://helix.ml/threat-watch/i/cisco-secure-email-gateway-cve-2026-76519 · Vulnerabilities · unknown · since 2026-10-14 · CVE-2026-76519
Cisco Secure Email Gateway contains a relative path traversal vulnerability that could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. CISA added CVE-2026-76519 to its Known Exploited Vulnerabilities catalog on Oct 14, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 17, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] GitLab: Unauthenticated RCE via Ruby Onigmo regex compiler integer overflow across all releases since 7.0 (CVE-2026-110264)
https://helix.ml/threat-watch/i/gitlab-unauthenticated-rce-via-ruby-onigmo-regex-compiler-integer-overflow-across-all-releases-since-7-0-cve-2026-110264 · Vulnerabilities · patched · since 2026-10-21 · CVE-2026-100104, CVE-2026-100755, CVE-2026-101168, CVE-2026-103515, CVE-2026-103549, CVE-2026-104661, CVE-2026-105458, CVE-2026-105711, CVE-2026-105777, CVE-2026-110264, CVE-2026-112212, CVE-2026-112326, CVE-2026-112378, CVE-2026-12664, CVE-2026-13319, CVE-2026-14210, CVE-2026-14288, CVE-2026-14552, CVE-2026-14814, CVE-2026-15723, CVE-2026-16255, CVE-2026-16275, CVE-2026-16301, CVE-2026-5954, CVE-2026-6567, CVE-2026-7767, CVE-2026-78335, CVE-2026-81839, CVE-2026-82632, CVE-2026-84284, CVE-2026-85529, CVE-2026-89078, CVE-2026-92528, CVE-2026-9268, CVE-2026-92883, CVE-2026-93577, CVE-2026-96893, CVE-2026-97229
GitLab patched CVE-2026-110264 (CVSS 10.0), an unauthenticated RCE caused by an integer overflow in Ruby's Onigmo regex compiler, which GitLab bundles and ships. It affects every self-managed GitLab version since 7.0 (2014); the Oct 12 fix for the earlier CVE-2026-97229 covered only 19.2+, so instances patched then are vulnerable again. It is the fourth Onigmo RCE reported by researcher joaxcar in a month (two 9.9 auth-required, two 10.0 unauthenticated). Ruby released 4.0.9, 3.4.12, and 3.3.13 fixing three underlying bugs; Ruby 3.2 and earlier get no fix. No exploitation or CISA KEV listing as of Oct 23; no workaround exists. GitLab also fixed 10 other issues including an 8.2 account-takeover and a 7.5 OAuth/OIDC cache-poisoning flaw.
Fixed: GitLab 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13; Ruby 4.0.9, 3.4.12, 3.3.13
Do: Upgrade self-managed GitLab immediately to 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, or 18.11.13 — instances patched on Oct 12 are still vulnerable; Plan for downtime on single-node upgrades (19.4.3/19.3.6 include database migrations); use zero-downtime procedure on multi-node; Deploy GitLab's TLDR Sigma detection rules ('Onigmo native worker crash', 'Org mode render error burst') to hunt exploitation attempts; Upgrade Ruby to 4.0.9, 3.4.12, or 3.3.13 in any Ruby app compiling regexes from untrusted input; note Regexp.timeout and pattern-length caps do not mitigate; Migrate off Ruby 3.2 (EOL, unfixed) or stop compiling attacker-controlled patterns via Regexp.new/union/compile or interpolation; Review SAML+LDAP auto-linking and shared-cache OAuth/OIDC setups against CVE-2026-15723 and CVE-2026-112212

### [high] Electron: compromised eMudhra intermediate certificates allow TLS server impersonation (CVE-2026-115570)
https://helix.ml/threat-watch/i/electron-compromised-emudhra-intermediate-certificates-allow-tls-server-impersonation-cve-2026-115570 · Supply chain · patched · since 2026-10-22 · CVE-2026-111943, CVE-2026-113470, CVE-2026-115557, CVE-2026-115570
A set of eMudhra intermediate CA certificates was compromised and is being blocked by browsers and other TLS clients. Electron releases before the patched versions did not block these intermediates in either Chromium networking or Node.js tls/https/fetch, so an attacker holding a certificate issued via the compromised intermediates and able to intercept network traffic (e.g. on-path/MitM) could impersonate a TLS server to an Electron app. Only apps making TLS network connections are affected; offline apps are not. Go (CVE-2026-111943) and Firefox (CVE-2026-113470) shipped the same mitigation. There are no app-side workarounds; fixed releases are 45.0.0-beta.6, 44.9.1, 43.8.1 and 42.11.16, published 2026-10-22/23.
Fixed: 45.0.0-beta.6; 44.9.1; 43.8.1; 42.11.16
Do: Upgrade Electron to 45.0.0-beta.6, 44.9.1, 43.8.1 or 42.11.16 (or later) and rebuild/redistribute apps, prioritising apps that make TLS connections over untrusted networks; Audit which Electron apps in your estate make network connections and prioritise those handling sensitive data; Verify no pinned or custom certificate logic bypasses the new block; confirm updated builds ship the mitigation in both Chromium and Node.js TLS paths; Monitor for any further eMudhra-related revocations or advisories affecting other TLS clients in your stack

### [critical] BeyondTrust Remote Support Authentication Bypass by Spoofing Vulnerability (CVE-2026-102764)
https://helix.ml/threat-watch/i/beyondtrust-remote-support-cve-2026-102764 · Vulnerabilities · unknown · since 2026-10-16 · CVE-2026-102764
BeyondTrust Remote Support contains an authentication bypass by spoofing vulnerability that could allow a remote attacker to perform file operations on the appliance. CISA added CVE-2026-102764 to its Known Exploited Vulnerabilities catalog on Oct 16, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 19, 2026 (BOD 22-01); treat that as the outer limit.

### [high] Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability (CVE-2026-104935)
https://helix.ml/threat-watch/i/ivanti-connect-secure-cve-2026-104935 · Vulnerabilities · unknown · since 2026-10-13 · CVE-2026-104935
Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands. CISA added CVE-2026-104935 to its Known Exploited Vulnerabilities catalog on Oct 13, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 16, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] Pillow: Critical RCE flaws in Python image library via crafted EPS filenames and JPEG/TIFF buffers (CVE-2026-112900, CVE-2026-112403, CVE-2026-112393)
https://helix.ml/threat-watch/i/pillow-critical-rce-flaws-in-python-image-library-via-crafted-eps-filenames-and-jpeg-tiff-buffers-cve-2026-112900-cve-20 · Vulnerabilities · patched · since 2026-10-16 · CVE-2026-112393, CVE-2026-112398, CVE-2026-112403, CVE-2026-112900
Pillow, the most widely used Python image library (~436M downloads/month), fixed a batch of vulnerabilities in version 13.0.0 released 2026-10-16. The headline flaw, CVE-2026-112900, lets an attacker run OS commands by controlling the filename of an EPS image, which Pillow passes unvalidated to Ghostscript; it affects versions 2.6.0–12.3.0 and only hosts with the gs binary installed. Two maintainer-critical fixes cover a stale-image-data memory bug and JPEG decoding overflows, including an FPX flaw enabling RCE from a single Image.open() call when olefile is installed, and CVE-2026-112403, a lossless-JPEG thumbnail buffer overflow. CVE-2026-112393, present since 2013, overflows a buffer when saving compressed TIFFs to in-memory buffers. No exploitation is known; a public PoC exists for the TIFF flaw. One JPEG flaw was found by Anthropic using Claude and validated by Ada Logics.
Fixed: 13.0.0
Do: Upgrade to Pillow 13.0.0 and rebuild containers, wheels, and base images bundling older copies; note Python 3.10 is dropped, so ensure Python 3.11+; Until upgraded, keep the Ghostscript gs binary off hosts processing untrusted uploads and never pass attacker-controlled filenames to Image.open() for EPS; Avoid draft()/thumbnail() on untrusted JPEGs, or call load() first or pass reducing_gap=None; Treat saving user-supplied TIFF images to in-memory buffers (e.g. io.BytesIO) as a sensitive path

### [high] Palo Alto Networks PAN-OS Code Injection Vulnerability (CVE-2026-0322)
https://helix.ml/threat-watch/i/palo-alto-networks-pan-os-cve-2026-0322 · Vulnerabilities · unknown · since 2026-10-14 · CVE-2026-0322
Palo Alto Networks PAN-OS contains a code injection vulnerability that could allow an authenticated attacker with network access to execute arbitrary code with root privileges on the firewall. CISA added CVE-2026-0322 to its Known Exploited Vulnerabilities catalog on Oct 14, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 17, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] Collabora Online – Built-in CODE Server OS Command Injection Vulnerability (CVE-2026-110447)
https://helix.ml/threat-watch/i/collabora-collabora-online-built-in-code-server-cve-2026-110447 · Vulnerabilities · unknown · since 2026-10-23 · CVE-2026-110447
Collabora Collabora Online – Built-in CODE Server when used within the NextCloud platform contains an OS command injection vulnerability that allows for remote code execution when the CODE server isn't running. CISA added CVE-2026-110447 to its Known Exploited Vulnerabilities catalog on Oct 23, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 26, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] Brotli (Google/PyPI): out-of-bounds write in Brotli decoder allows RCE via crafted compressed stream (CVE-2026-111497)
https://helix.ml/threat-watch/i/brotli-google-pypi-out-of-bounds-write-in-brotli-decoder-allows-rce-via-crafted-compressed-stream-cve-2026-111497 · Vulnerabilities · patched · since 2026-10-22 · CVE-2026-111497
A buffer overflow (out-of-bounds write) in the Brotli decoder in Google Brotli 1.0.3 through 1.2.0, dubbed "Node2Shell", allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory, cause denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. The flaw affects all platforms and also impacts the PyPI brotli and brotlicffi packages (>=1.0.3, <1.2.1) and Node.js, which disclosed it in its October 2026 security releases. No in-the-wild exploitation is reported. Fixed versions are 1.0.10, 1.1.1, and 1.2.1 (brotlicffi 1.2.1.0); organisations should upgrade any affected Brotli libraries or binaries.
Fixed: brotli 1.2.1; brotlicffi 1.2.1.0; Google Brotli 1.0.10 / 1.1.1 / 1.2.1
Do: Upgrade PyPI brotli to >=1.2.1 and brotlicffi to >=1.2.1.0 wherever installed; Upgrade any Brotli C library or binary builds from 1.0.3–1.2.0 to 1.0.10, 1.1.1, or 1.2.1; Update Node.js runtimes to the patched October 2026 security release versions; Audit services that decompress untrusted Brotli input (HTTP content-encoding, build pipelines) and prioritise patching internet-facing ones; Rebuild/redeploy dependent containers and binaries linked against the vulnerable Brotli decoder

### [critical] Arista VeloCloud Orchestrator SQL Injection Vulnerability (CVE-2026-114625)
https://helix.ml/threat-watch/i/arista-velocloud-orchestrator-cve-2026-114625 · Vulnerabilities · unknown · since 2026-10-23 · CVE-2026-114625
Arista VeloCloud Orchestrator on-prem contains a SQL injection vulnerability that may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator. CISA added CVE-2026-114625 to its Known Exploited Vulnerabilities catalog on Oct 23, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 26, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] DOMPurify: SAFE_FOR_TEMPLATES bypass lets template expressions survive in shadow root content on DOM output modes (GHSA-cg2g-xh64-v4q7)
https://helix.ml/threat-watch/i/dompurify-safe-for-templates-bypass-lets-template-expressions-survive-in-shadow-root-content-on-dom-output-modes-ghsa-cg · Vulnerabilities · patched · since 2026-10-12 · CVE-2026-65900
DOMPurify 3.4.4 through 3.4.16 fails to scrub template expressions ({{...}}, ${...}, <%...%>) inside attached shadow roots when SAFE_FOR_TEMPLATES is enabled with a DOM-returning mode (RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE). The post-walk safety net _scrubTemplateExpressions recurses into <template>.content but not shadow roots, so an attacker-supplied expression split across text nodes separated by disallowed elements reassembles after sanitization and can be evaluated by a downstream template engine, yielding XSS or server-side template injection. Declarative shadow DOM via setHTMLUnsafe also reaches the gap. Exploitation requires non-default configuration and downstream template evaluation. Fixed in DOMPurify 3.4.17; a public proof of concept exists but no in-the-wild exploitation is known.
Fixed: 3.4.17
Do: Upgrade dompurify to 3.4.17 or later immediately if using SAFE_FOR_TEMPLATES with any DOM-returning mode; Audit whether your app passes DOM nodes with attached shadow roots (including declarative shadow DOM parsed via setHTMLUnsafe/parseHTMLUnsafe) into DOMPurify; Review whether sanitized shadow root text content is fed into a template engine; add independent escaping/scrubbing there as defense in depth; If upgrading is not immediately possible, disable SAFE_FOR_TEMPLATES or DOM-returning modes, or post-process shadow root content yourself before template evaluation

### [medium] Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability (CVE-2026-96652)
https://helix.ml/threat-watch/i/plex-media-server-cve-2026-96652 · Vulnerabilities · unknown · since 2026-10-20 · CVE-2026-96652
Plex Media Server contains a server-side request forgery (SSRF) vulnerability which could allow an attacker using any X-Plex-Token value to include a full URL in the 'protocol' parameter and force the Plex server to POST to the attacker's chosen destination. This vulnerability can be chained with CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656. CISA added CVE-2026-96652 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Nov 3, 2026 (BOD 22-01); treat that as the outer limit.

### [high] IO::Compress::Brotli (Perl): bundled brotli decoder out-of-bounds write allows memory disclosure, crashes, or potential RCE when decompressing untrusted data (CVE-2026-115936)
https://helix.ml/threat-watch/i/io-compress-brotli-perl-bundled-brotli-decoder-out-of-bounds-write-allows-memory-disclosure-crashes-or-potential-rce-whe · Supply chain · patched · since 2026-10-23 · CVE-2026-111497, CVE-2026-115936
The CPAN Security Group disclosed CVE-2026-115936: IO::Compress::Brotli versions from 0.004001 before 0.023 bundle a copy of the brotli library (1.0.4 through 1.2.0) containing an out-of-bounds write in the decoder (CVE-2026-111497). Because the module compiles the bundled brotli rather than linking the system library, upgrading system brotli does not remediate. Any application decompressing untrusted data via unbro or the decompress method is exposed: a crafted brotli stream can corrupt decoder state, disclose memory, crash the process, or potentially execute arbitrary code. Version 0.023, released 2026-10-23, updates the bundled brotli to 1.2.1 and fixes the issue. No in-the-wild exploitation reported.
Fixed: 0.023
Do: Upgrade IO-Compress-Brotli to 0.023 or later and rebuild/redeploy dependent applications; Audit Perl codebases and dependencies for use of IO::Compress::Brotli, especially paths decompressing untrusted input; Until patched, restrict or sandbox processing of untrusted brotli-compressed data

### [critical] x402 SDKs: Critical flaws let malicious APIs drain AI agents' token balances, bypass Solana payments, and relay login signatures (no CVEs assigned)
https://helix.ml/threat-watch/i/x402-sdks-critical-flaws-let-malicious-apis-drain-ai-agents-token-balances-bypass-solana-payments-and-relay-login-signat · Vulnerabilities · patched · since 2026-10-22
Security firm V12 disclosed three critical flaws in the x402 payment SDKs used by AI agents to pay for API calls. The default client set no spending limit, letting a malicious API request an agent's full token balance; the TypeScript Solana facilitator accepted token approvals (moving no tokens) as valid payments, enabling complete payment bypass; and the SIWx sign-in client signed login messages without verifying the destination site, enabling relayed authentication. All three were fixed in August 18 releases (2.23.0+), which add $1-per-payment caps, stablecoin-only defaults, instruction-type checks, and domain verification. No attacks reported, but npm/PyPI audits give no warning to upgrade. Latest versions: 2.28.0 (TypeScript/Go), 2.25.0 (Python).
Fixed: @x402/core, @x402/svm, @x402/extensions, @x402/fetch, @x402/axios 2.28.0; Go v2.28.0; Python 2.25.0; minimum 2.23.0 for the three critical fixes
Do: Upgrade @x402/fetch, @x402/axios, @x402/extensions, @x402/svm to 2.23.0+ (latest 2.28.0); Python to 2.25.0; Go to v2.28.0; If unable to upgrade, register a payment policy (registerPolicy / register_policy max_amount) that drops payment options above a set amount; Do not pass spendControls: false; review any apps that disable spend controls; Verify SIWx login messages identify the site being contacted before signing; Audit agent wallets for unexpected balance drains or unauthorized approvals

### [critical] mem0ai: SQL injection in Databricks vector store lets attackers execute SQL via crafted memory content (CVE-2026-115324)
https://helix.ml/threat-watch/i/mem0ai-sql-injection-in-databricks-vector-store-lets-attackers-execute-sql-via-crafted-memory-content-cve-2026-115324 · Vulnerabilities · patched · since 2026-10-22 · CVE-2026-115324
A SQL injection vulnerability (CVE-2026-115324) was disclosed on 2026-10-22 in mem0ai's Databricks vector store (mem0/vector_stores/databricks.py). Versions 0.1.117 through before 1.0.8 pass attacker-influenced memory text, metadata, or message names into unescaped string interpolation in insert() and update() calls, allowing injection of arbitrary SQL against the configured Databricks SQL warehouse. Any application storing untrusted user content in mem0 memories backed by the Databricks vector store is affected, with high confidentiality, integrity, and availability impact. No in-the-wild exploitation is reported. Fixed in mem0ai 1.0.8 (commit a2ffca3), which escapes/parameterizes the affected queries.
Fixed: mem0ai 1.0.8
Do: Upgrade mem0ai to 1.0.8 or later immediately if you use the Databricks vector store; If upgrading is delayed, restrict or disable the Databricks vector store path and sanitize/validate memory text, metadata, and message names before storage; Review Databricks SQL warehouse logs for signs of injected or anomalous queries; Limit the SQL warehouse credentials used by mem0 to least privilege to contain potential injection impact; Audit any stored memories for suspicious content that may have been used as an injection vector

### [critical] Pillow: multi-frame image loaders reuse stale native buffers after mode transitions, enabling OOB writes and RCE (CVE-2026-96639)
https://helix.ml/threat-watch/i/pillow-multi-frame-image-loaders-reuse-stale-native-buffers-after-mode-transitions-enabling-oob-writes-and-rce-cve-2026 · Vulnerabilities · patched · since 2026-10-22 · CVE-2026-96639
Pillow multi-frame image loaders (PSD, MPO/JPEG, DCX, MIC) can retain native ImagingCore storage allocated for one frame while a later frame changes the image mode and decoder tiles. ImageFile.load_prepare() only reallocates storage when _im is None and does not verify the retained buffer matches the current mode/size, so a crafted file with frame 0 in a narrow mode (e.g. L) and frame 1 in a wider mode (RGB/CMYK) causes native out-of-bounds writes, crashes, and over-reads. The researcher demonstrated command execution via the documented ImageSequence.Iterator + frame.load() path, including a one-request unauthenticated web-upload exploit. All Pillow users processing untrusted images (web upload services especially) are affected. Fixed in Pillow 13.0.0, published 2026-10-22.
Fixed: 13.0.0
Do: Upgrade Pillow to 13.0.0 immediately, prioritising internet-facing services that process user-uploaded images; If upgrade is not immediate, restrict or sandbox image processing of untrusted uploads (e.g. isolate in containers/worker processes with limited privileges); Block or reject multi-frame MPO/PSD/DCX/MIC uploads at ingestion until patched; Audit image-processing pipelines for Pillow versions >= 11.0.0, < 13.0.0 and monitor for crash anomalies indicating exploitation attempts

### [critical] Apache Traffic Server: 15 vulnerabilities fixed including critical magick plugin command injection and request smuggling flaws (CVE-2026-111813 et al.)
https://helix.ml/threat-watch/i/apache-traffic-server-15-vulnerabilities-fixed-including-critical-magick-plugin-command-injection-and-request-smuggling · Vulnerabilities · patched · since 2026-10-20 · CVE-2025-31699, CVE-2025-55702, CVE-2026-111804, CVE-2026-111805, CVE-2026-111808, CVE-2026-111813, CVE-2026-111816
The Apache Software Foundation announced fixes for 15 vulnerabilities in Apache Traffic Server, addressed in versions 9.2.16, 10.1.5 and 10.2.1. The most severe (CVE-2026-111813, CVSS 10.0) lets an unauthenticated client control ImageMagick convert arguments via the experimental magick plugin's default configuration. Other issues include a wasm plugin use-after-free and unvalidated metric IDs (CVE-2026-111804), request smuggling via reused origin connections owed a request body (CVE-2025-31699) and unread Expect: 100-continue bodies (CVE-2025-55702), cache poisoning via a malformed 302 bypassing parse-error rejection (CVE-2026-111816), and HTTP/2-triggered origin worker-pool exhaustion (CVE-2026-111805, CVE-2026-111808). All ATS versions 9.0.0 through 10.2.0 are affected; no in-the-wild exploitation is reported. Fixes are available in the new releases.
Fixed: 9.2.16; 10.1.5; 10.2.1
Do: Upgrade to ATS 9.2.16, 10.1.5 or 10.2.1 immediately, prioritising internet-facing deployments; Disable or remove the experimental magick and wasm plugins if not strictly needed, especially on unpatched instances; Review access controls and front-end proxy connection sharing given the request smuggling and cache poisoning flaws; Monitor for signs of cache poisoning or request desync in logs after upgrading

### [critical] Fortinet FortiSIEM: Public PoC exploit released for unauthenticated RCE via path traversal and NUL-byte file overwrite (CVE-2026-106173)
https://helix.ml/threat-watch/i/fortinet-fortisiem-public-poc-exploit-released-for-unauthenticated-rce-via-path-traversal-and-nul-byte-file-overwrite-cv · Vulnerabilities · patched · since 2026-10-20 · CVE-2026-106173
Researchers at Horizon3.ai published a proof-of-concept exploit for CVE-2026-106173 (CVSS 9.4), a critical path traversal flaw in Fortinet FortiSIEM allowing unauthenticated remote code execution. The gRPC QueryResultReq handler on TCP port 27918 processes a user-supplied 'query-id' without validation, letting attackers traverse directories and embed a NUL byte to truncate the appended filename and overwrite arbitrary files. The PoC overwrites /opt/charting/redishb.sh, a Redis health-check script run by cron every 60 seconds, converting the arbitrary-file-write into code execution. Fortinet patched the flaw last week: FortiSIEM 7.5.0 users must upgrade to 7.5.1 or above; 7.6 is not affected. With a public PoC available, organisations running affected versions face imminent exploitation risk.
Fixed: FortiSIEM 7.5.1 or above (7.6 not affected)
Do: Upgrade FortiSIEM 7.5.0 to 7.5.1 or above immediately; Restrict network access to TCP port 27918 (gRPC service) from untrusted networks; Check /opt/charting/redishb.sh and similar cron-run scripts for tampering; Hunt for signs of exploitation, including unexpected writes or cron-executed script modifications; Monitor Fortinet advisories for additional affected branches

### [critical] Chrome: stable update fixes 353 security flaws incl. critical memory corruption (CVE-2026-113341, CVE-2026-113279, CVE-2026-113072, CVE-2026-113280)
https://helix.ml/threat-watch/i/chrome-stable-update-fixes-353-security-flaws-incl-critical-memory-corruption-cve-2026-113341-cve-2026-113279-cve-2026-1 · Vulnerabilities · patched · since 2026-10-20 · CVE-2026-112992, CVE-2026-112993, CVE-2026-112994, CVE-2026-112995, CVE-2026-112996, CVE-2026-112997, CVE-2026-112998, CVE-2026-112999, CVE-2026-113000, CVE-2026-113001, CVE-2026-113002, CVE-2026-113003, CVE-2026-113004, CVE-2026-113005, CVE-2026-113006, CVE-2026-113007, CVE-2026-113008, CVE-2026-113009, CVE-2026-113010, CVE-2026-113011
On 2026-10-20 Google promoted Chrome 156 to the stable channel for Windows, Mac and Linux, rolling out over coming days/weeks. Versions 156.0.8078.47 (Linux) and 156.0.8078.47/.48 (Windows/Mac) contain 353 security fixes, including several critical memory corruption vulnerabilities in Skia, Accessibility, and CSS (CVE-2026-113341, CVE-2026-113279, CVE-2026-113072, CVE-2026-113280), reported by Google and Xinyang Ge in early October 2026. Bug details and links are restricted until a majority of users are updated. No in-the-wild exploitation is mentioned. All users of Chrome on desktop platforms are affected until updated; the fix is delivered in the 156 stable release.
Fixed: 156.0.8078.47 (Linux); 156.0.8078.47/.48 (Windows/Mac)
Do: Update Chrome to 156.0.8078.47/.48 or later on all managed Windows, Mac and Linux endpoints as soon as the rollout reaches your channel; Force browser auto-update or push the update via enterprise policy (Update policies / MDM) and verify versions in your fleet; If you manage Chromium-based browsers (Edge, Brave, etc.), track their rebuilds of the same underlying fixes and patch accordingly; Restrict browsing of untrusted content via other controls until fleet updates complete

### [high] EG Secure Solutions SiteGuard Server Edition OS Command Injection Vulnerability (CVE-2026-106931)
https://helix.ml/threat-watch/i/eg-secure-solutions-siteguard-server-edition-cve-2026-106931 · Vulnerabilities · unknown · since 2026-10-20 · CVE-2026-106931
EG Secure Solutions SiteGuard Server Edition contains an OS command injection vulnerability which may allow an attacker to execute arbitrary OS commands with root or SYSTEM privileges on the system running the affected product. CISA added CVE-2026-106931 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 23, 2026 (BOD 22-01); treat that as the outer limit.

### [high] Plex Media Server External Control of File Name or Path Vulnerability (CVE-2026-96656)
https://helix.ml/threat-watch/i/plex-media-server-cve-2026-96656 · Vulnerabilities · unknown · since 2026-10-20 · CVE-2026-96656
Plex Media Server contains an external control of file name or path vulnerability which can allow an admin user to write arbitrary files that may be executed on load. This vulnerability can be chained with CVE-2026-96652, CVE-2026-96654, and CVE-2026-96655. CISA added CVE-2026-96656 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 23, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Plex Media Server Server-Side Request Forgery (SSRF) Vulnerability (CVE-2026-96655)
https://helix.ml/threat-watch/i/plex-media-server-cve-2026-96655 · Vulnerabilities · unknown · since 2026-10-20 · CVE-2026-96655
Plex Media Server contains a server-side request forgery (SSRF) vulnerability that could allow an authenticated user to request arbitrary internal or external addresses via the '/video/:/transcode/universal' path parameter. This vulnerability can be chained with CVE-2026-96652, CVE-2026-96654, and CVE-2026-96656. CISA added CVE-2026-96655 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Nov 3, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Plex Media Server Improper Neutralization of Encoded URI Schemes in a Web Page Vulnerability (CVE-2026-96654)
https://helix.ml/threat-watch/i/plex-media-server-cve-2026-96654 · Vulnerabilities · unknown · since 2026-10-20 · CVE-2026-96654
Plex Media Server contains an improper neutralization of encoded URI schemes in a web page vulnerability that could allow an attacker to call other plugins' functions and supply their own parameters. This vulnerability can be chained with CVE-2026-96652, CVE-2026-96655, and CVE-2026-96656. CISA added CVE-2026-96654 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 23, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Siemens Software Center Uncontrolled Search Path Element Vulnerability (CVE-2026-110936)
https://helix.ml/threat-watch/i/siemens-software-center-cve-2026-110936 · Vulnerabilities · patched · since 2026-10-20 · CVE-2026-110936
Siemens Software Center contains an uncontrolled search path element vulnerability that 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. CISA added CVE-2026-110936 to its Known Exploited Vulnerabilities catalog on Oct 20, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Nov 3, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Assurance Retraite data breach: 70K accounts exposed
https://helix.ml/threat-watch/i/assuranceretraite-data-breach · Breaches · no-fix-needed · since 2026-10-20
In September 2024, the French national pension fund Assurance Retraite suffered a data breach affecting approximately 370k assistance beneficiaries. The data included 70k unique email addresses along with names, dates of birth, physical addresses, phone numbers, income levels, marital statuses, French social security numbers (NIR) and contact details of relatives or other nominated contacts. In its disclosure notice, Assurance Retraite attributed the breach to a compromised partner account. Exposed data: dates of birth, email addresses, family members' names, government issued ids, income levels, marital statuses, names, phone numbers, physical addresses. The breach dates from Sep 1, 2024; Have I Been Pwned loaded it on Oct 20, 2026.
Do: If you had a Assurance Retraite account, change its password and the password of any other account that reused it.; Turn on multi-factor authentication wherever it is offered.; Check whether your addresses are in this breach at https://haveibeenpwned.com.; Expect targeted phishing that quotes the leaked details; verify any unexpected contact out of band.

### [critical] Wasmtime: Cranelift bit-packing overflow enables sandbox escape via crafted Wasm module (CVE-2026-115889)
https://helix.ml/threat-watch/i/wasmtime-cranelift-bit-packing-overflow-enables-sandbox-escape-via-crafted-wasm-module-cve-2026-115889 · Vulnerabilities · patched · since 2026-10-19 · CVE-2026-115889
Wasmtime's Cranelift compiler backend bit-packs SSA value indices in a way that can silently overflow in release builds, producing incorrect value references in the IR and arbitrary miscompilation. A very large or specially crafted Wasm function using many SSA values can force type confusion or other side effects and escape the sandbox. Any Wasmtime engine using default settings (Cranelift backend) on any architecture is affected, making this critical for anyone running untrusted Wasm modules. Fixed in Wasmtime v36.0.19 (backport) and v43.0.0, where Cranelift now uses a full u32 index with explicit limit checks. No public exploitation reported; EPSS 0.66%.
Fixed: 36.0.19; 43.0.0
Do: Upgrade Wasmtime to v36.0.19 or v43.0.0 immediately if you run untrusted Wasm modules; If upgrading is not immediately possible, restrict or sandbox which Wasm modules are executed and avoid running untrusted module bodies; Audit dependencies and services that embed Wasmtime (e.g. Rust services, Fastly/Lucene-style runtimes) and rebuild against the patched version; Monitor for suspicious Wasm module workloads or crashes that could indicate exploitation attempts

### [high] PingCAP (TiDB Cloud): Extortion group FulcrumSec used stolen service account credentials to access internal systems, copying business data and source code
https://helix.ml/threat-watch/i/pingcap-tidb-cloud-extortion-group-fulcrumsec-used-stolen-service-account-credentials-to-access-internal-systems-copying · Breaches · no-fix-needed · since 2026-10-19
On Oct 19, 2026, PingCAP disclosed that extortion group FulcrumSec breached its internal systems between Sept 9 and Oct 7 using stolen service account credentials, copying data and source code. Forensics found no evidence attackers accessed customer TiDB databases or ran malicious commands, but exported records included TiDB Cloud account info, billing/contract details, email addresses, SQL editor text, encrypted API keys, and a four-year log of customer connections. FulcrumSec claims broader access (financial records, Google Cloud files, Jira, CRM, analytics) and named ~2,500+ affected organizations including Airbnb, Booking.com, Baidu, Fujitsu, Capcom, Konami, and Square Enix. PingCAP has invalidated compromised credentials, fixed four reported vulnerabilities, and advised API key rotation.
Do: Rotate TiDB Cloud management API keys immediately and audit for anomalous usage; Be alert for targeted phishing using stolen billing/contract/contact data; brief staff and verify vendor communications out-of-band; Review exposed account and usage data for sensitive contents and assess downstream compliance/notification obligations; Monitor PingCAP's Trust Hub for customer-specific impact confirmations; Harden service account credentials and access paths for cloud vendors holding business data

### [critical] Linux KVM: guest-to-host escape via malformed IPv4 checksum metadata lets guest VMs compromise the host (CVE-2026-99999)
https://helix.ml/threat-watch/i/linux-kvm-guest-to-host-escape-via-malformed-ipv4-checksum-metadata-lets-guest-vms-compromise-the-host-cve-2026-99999 · Vulnerabilities · patched · since 2026-10-19 · CVE-2026-99999
Researcher Paulos Yibelo disclosed 'PwnEscape', a critical (CVSS 9.3) guest-to-host escape in Linux KVM, tracked as CVE-2026-99999. A guest can send malformed IPv4 packets whose checksum metadata causes skb_checksum_help to corrupt the network header, letting untrusted guest-controlled metadata rewrite security-sensitive packet fields after kernel validation. Red Hat says impact may include arbitrary code execution on the host, denial of service, or sensitive memory disclosure, breaking guest-host isolation. Yibelo describes it as a novel attack class in Linux networking. AWS EC2 says it is not at risk and Google Cloud is likely unaffected. An upstream kernel fix is rolling into Debian, RHEL, Ubuntu and KVM-based products like Nutanix and Proxmox.
Do: Patch KVM hosts with the fixed kernel as it reaches your distro (Debian, RHEL, Ubuntu) and restart/evacuate workloads as required; Prioritise hosts running untrusted or multi-tenant guest workloads; Verify virtualization products built on KVM (Proxmox, Nutanix, custom stacks) have shipped the fix before exposing new tenants; Review whether guest workloads can send arbitrary network traffic to the host and apply compensating network filtering where patching is delayed; Monitor vendor advisories for exploitation reports

### [critical] Laravel: TokenGuard authentication bypass via non-string API credentials allows account takeover (CVE-2026-114509)
https://helix.ml/threat-watch/i/laravel-tokenguard-authentication-bypass-via-non-string-api-credentials-allows-account-takeover-cve-2026-114509 · Vulnerabilities · patched · since 2026-10-19 · CVE-2026-114509
A critical authentication bypass (CVE-2026-114509, CVSS 9.2) was disclosed in Laravel's built-in TokenGuard. When a standard token-based API guard is configured, an unauthenticated attacker can submit a specially crafted non-string credential value that is mishandled during the authentication lookup; under certain MySQL/MariaDB database configurations the query matches an unintended user record, letting the attacker authenticate as an arbitrary existing user without knowing their API token. Any route protected by the affected guard is exposed to account takeover. Fixes were released in laravel/framework 12.68.0 and 13.29.0 on 2026-10-19/23; no in-the-wild exploitation is known.
Fixed: laravel/framework 13.29.0; laravel/framework 12.68.0
Do: Upgrade laravel/framework to 12.68.0 (Laravel 12) or 13.29.0 (Laravel 13) immediately; Audit applications for use of token-based API guards and treat those routes as exposed until patched; Review auth logs for anomalous API token authentication or unexpected user sessions; If immediate upgrade is not possible, add middleware or validation rejecting non-string API token credentials; Verify database configuration (MySQL/MariaDB collation/type coercion behaviour) and consider hardening token column comparisons

### [medium] Gîtes de France data breach: 117K accounts exposed
https://helix.ml/threat-watch/i/gitesdefrance-data-breach · Breaches · no-fix-needed · since 2026-10-18
In May 2026, the French holiday rental network Gîtes de France suffered a data breach affecting some of its departmental branches. The incident exposed hundreds of thousands of customer records, including 118k unique email addresses alongside names, phone numbers, postal addresses and booking details. Exposed data: booking details, email addresses, names, phone numbers, physical addresses. The breach dates from May 16, 2026; Have I Been Pwned loaded it on Oct 18, 2026.
Do: If you had a Gîtes de France account, change its password and the password of any other account that reused it.; Turn on multi-factor authentication wherever it is offered.; Check whether your addresses are in this breach at https://haveibeenpwned.com.; Expect targeted phishing that quotes the leaked details; verify any unexpected contact out of band.

### [high] Pillow: bundled libopenjp2 heap-buffer-overflow write reachable from Image.open().load() (OSV-2025-219 / GHSA-78g4-xqwv-q3g8)
https://helix.ml/threat-watch/i/pillow-bundled-libopenjp2-heap-buffer-overflow-write-reachable-from-image-open-load-osv-2025-219-ghsa-78g4-xqwv-q3g8 · Supply chain · partial · since 2026-10-17
Pillow wheels from 11.1.0 through 12.3.0 bundle a libopenjp2 (2.5.3/2.5.4) containing a heap-buffer-overflow write in opj_j2k_read_sod (OSV-2025-219), introduced in OpenJPEG in June 2024 — notably, older OpenJPEG 2.5.2 is safe. The flaw is reachable from Image.open(fp); im.load() with default settings, and because the wheel bundles its own copy, patched host OS libraries do not help. A public ASan PoC demonstrates the overflow through Pillow's own decoder. Attackers can craft a JPEG 2000 codestream that triggers memory corruption even when uploaded as avatar.png with image/png Content-Type, since Image.open() sniffs magic bytes. Fixed in Pillow 13.0.0; the upstream OpenJPEG fix (91d08b11, Feb 2026) remains unreleased. No in-the-wild exploitation reported.
Fixed: pillow 13.0.0
Do: Upgrade Pillow to 13.0.0 (or pin to <=11.0.0 if downgrade is feasible); Until upgraded, pass an explicit formats= list excluding JPEG2000 to Image.open() and validate on the detected format, not client Content-Type or filename; Reject or sandbox untrusted image uploads; consider blocking JPEG 2000 magic bytes (JP2/j2k codestreams) at the application layer; Audit image-processing services for reliance on filename/Content-Type allowlists that Image.open() bypasses; Monitor for an OpenJPEG release carrying 91d08b11 and rebuild any vendored/bundled OpenJPEG accordingly

### [medium] Fortinet Multiple Products Path Traversal Vulnerability (CVE-2025-61624)
https://helix.ml/threat-watch/i/fortinet-multiple-products-cve-2025-61624 · Vulnerabilities · unknown · since 2026-10-16 · CVE-2025-61624
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. CISA added CVE-2025-61624 to its Known Exploited Vulnerabilities catalog on Oct 16, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 19, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] Google Chrome: Extended Stable update fixes 10 security flaws including two critical CVEs (CVE-2026-110151, CVE-2026-110922)
https://helix.ml/threat-watch/i/google-chrome-extended-stable-update-fixes-10-security-flaws-including-two-critical-cves-cve-2026-110151-cve-2026-110922 · Vulnerabilities · patched · since 2026-10-15 · CVE-2026-110144, CVE-2026-110151, CVE-2026-110159, CVE-2026-110166, CVE-2026-110172, CVE-2026-110913, CVE-2026-110914, CVE-2026-110915, CVE-2026-110916, CVE-2026-110917, CVE-2026-110918, CVE-2026-110919, CVE-2026-110920, CVE-2026-110921, CVE-2026-110922
On 2026-10-15 Google released Chrome Extended Stable 152.0.7977.169 for Windows and Mac, fixing 10 security vulnerabilities: two Critical (CVE-2026-110151, CVE-2026-110922) and eight High severity issues (CVE-2026-110144, CVE-2026-110159, CVE-2026-110166, CVE-2026-110172, CVE-2026-110913, CVE-2026-110918, CVE-2026-110919, CVE-2026-110921). Google has not disclosed vulnerability types or exploit details, keeping bug information restricted until a majority of users are updated, which is standard practice and does not indicate active exploitation. No in-the-wild exploitation is reported. The update rolls out over the coming days/weeks; organisations managing Chrome via Extended Stable should ensure deployment of this build.
Fixed: 152.0.7977.169
Do: Deploy Chrome 152.0.7977.169 (Extended Stable) to all managed Windows and Mac endpoints as soon as it is available; Verify fleet versions via endpoint management/MDM and force browser updates where auto-update is disabled; Review whether any internal web apps rely on Extended Stable users and prioritise high-risk user groups; Monitor the Chrome Releases blog for the corresponding Stable channel release and any exploitation reports

### [high] Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability (CVE-2026-21589)
https://helix.ml/threat-watch/i/atlassian-multiple-products-cve-2026-21589 · Vulnerabilities · unknown · since 2026-10-15 · CVE-2026-21589
Multiple Atlassian products (Bitbucket Data Center ,Confluence Data Center, Jira Service Management Data Center, Jira Software Data Center, Bamboo Data Center, Crowd Data Center, Crucible and Fisheye) contain a files or directories accessible to external parties vulnerability which could allow an unauthenticated attacker to access specific files within the web application root directory in affected versions. CISA added CVE-2026-21589 to its Known Exploited Vulnerabilities catalog on Oct 15, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 18, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] Next.js: Unauthenticated RCE in `use cache` functions returning typed arrays (GHSA-673q-mjm6-r5xr)
https://helix.ml/threat-watch/i/next-js-unauthenticated-rce-in-use-cache-functions-returning-typed-arrays-ghsa-673q-mjm6-r5xr · Vulnerabilities · patched · since 2026-10-14
Vercel disclosed a critical (CVSS 9.5) unauthenticated remote code execution vulnerability in Next.js affecting App Router applications using Cache Components where a `use cache` function returns multiple typed arrays. All versions from 16.0.0 through 16.4.0 are affected; no workaround exists for applications with such cache functions, and Vercel urges immediate upgrades even for apps without similar functions. The advisory was published Oct 14, 2026 and last updated Oct 22, 2026. No in-the-wild exploitation is reported. The fix is available in Next.js 16.4.1 (commit a4cea6a).
Fixed: next 16.4.1
Do: Upgrade Next.js to 16.4.1 immediately, even if you don't use `use cache` functions; Audit App Router code for `use cache` functions returning multiple typed arrays; If upgrading is delayed, restrict exposure of affected apps at the edge/WAF and monitor for exploitation; Review Cache Components usage and re-test deployments after upgrade

### [critical] Next.js: Unauthenticated RCE in Image Optimization API via sharp memory vulnerability when SVG files are used (CVE-2026-96889)
https://helix.ml/threat-watch/i/next-js-unauthenticated-rce-in-image-optimization-api-via-sharp-memory-vulnerability-when-svg-files-are-used-cve-2026-96 · Vulnerabilities · patched · since 2026-10-14 · CVE-2026-96889
A critical (CVSS 9.5) unauthenticated remote code execution vulnerability (CVE-2026-96889) in Next.js was disclosed via GitHub Advisory GHSA-2464-fhr4-w9xw. The flaw stems from a memory-related vulnerability in the upstream sharp image-processing library used by Next.js's Image Optimization API, and is exploitable when SVG files are processed on glibc-based Linux deployments. All Next.js versions from 10.0.0 through 15.5.27 and 16.0.0 through 16.4.0 are affected. No in-the-wild exploitation is known. Fixes shipped in Next.js 15.5.28 and 16.4.1, which ensure package managers provide sharp >= 0.35.5; alternatively, operators can directly ensure sharp >= 0.35.5 as a workaround.
Fixed: next 15.5.28; next 16.4.1; sharp 0.35.5
Do: Upgrade Next.js to 15.5.28 or 16.4.1 (or later) and reinstall dependencies so sharp resolves to >= 0.35.5; If upgrading is not immediately possible, verify and pin sharp >= 0.35.5 in the dependency tree and redeploy; Audit deployments running on glibc-based Linux with the Image Optimization API exposed, especially where SVG inputs are processed; Check logs for suspicious requests to the image optimization endpoint and review for signs of exploitation

### [critical] Ahsay AhsayCBS Command Injection Vulnerability (CVE-2026-105134)
https://helix.ml/threat-watch/i/ahsay-ahsaycbs-cve-2026-105134 · Vulnerabilities · unknown · since 2026-10-14 · CVE-2026-105134
Ahsay AhsayCBS contains a command injection vulnerability that could allow a remote attacker to execute operating system commands via manipulation of the random parameter in the Replication Receiver component’s /rps/api/json/UpdateReceivers.do endpoint. This vulnerability can be chained with CVE-2026-105133. CISA added CVE-2026-105134 to its Known Exploited Vulnerabilities catalog on Oct 14, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 17, 2026 (BOD 22-01); treat that as the outer limit.

### [high] Ahsay AhsayCBS Improper Authentication Vulnerability (CVE-2026-105133)
https://helix.ml/threat-watch/i/ahsay-ahsaycbs-cve-2026-105133 · Vulnerabilities · unknown · since 2026-10-14 · CVE-2026-105133
Ahsay AhsayCBS contains an improper authentication vulnerability that could allow a remote attacker to bypass authentication via manipulation of the random parameter in the API component’s checkSysPwd function. This vulnerability can be chained with CVE-2026-105134. CISA added CVE-2026-105133 to its Known Exploited Vulnerabilities catalog on Oct 14, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 17, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Crunchbase data breach: 559K accounts exposed
https://helix.ml/threat-watch/i/crunchbase-data-breach · Breaches · no-fix-needed · since 2026-10-14
In January 2026, the private company intelligence platform Crunchbase was targeted in a ShinyHunters "pay or leak" extortion attempt. Data allegedly obtained from the company was subsequently published publicly and included 560k unique email addresses, largely belonging to leads and business contacts. Other data included names, physical addresses, phone numbers, job titles, employers and LinkedIn profiles. Crunchbase later confirmed that a threat actor had exfiltrated documents from its corporate network. Exposed data: email addresses, employers, job titles, names, phone numbers, physical addresses, social media profiles. The breach dates from Jan 22, 2026; Have I Been Pwned loaded it on Oct 14, 2026.
Do: If you had a Crunchbase account, change its password and the password of any other account that reused it.; Turn on multi-factor authentication wherever it is offered.; Check whether your addresses are in this breach at https://haveibeenpwned.com.; Expect targeted phishing that quotes the leaked details; verify any unexpected contact out of band.

### [critical] Fortinet FortiSandbox: two authentication bypass flaws in GUI and Fabric API allow unauthenticated attackers to access the management interface and API endpoints (CVE-2026-107656, CVE-2026-106172)
https://helix.ml/threat-watch/i/fortinet-fortisandbox-two-authentication-bypass-flaws-in-gui-and-fabric-api-allow-unauthenticated-attackers-to-access-th · Vulnerabilities · patched · since 2026-10-13 · CVE-2026-106172, CVE-2026-107656
On 2026-10-13 Fortinet published two PSIRT advisories for FortiSandbox and FortiSandbox Cloud. FG-IR-26-185 (CVE-2026-107656, CVSS 9.6) is an authentication bypass via alternate path (CWE-288) in the GUI letting a remote unauthenticated attacker bypass authentication with crafted HTTP requests, potentially executing unauthorized code; it affects FortiSandbox 4.4, 5.0 and 5.2 and the PaaS offering. FG-IR-26-179 (CVE-2026-106172, CVSS 4.9) is a hard-coded cryptographic key (CWE-321) in the Fabric API allowing unauthenticated access to some endpoints and privilege escalation, affecting dozens of FortiSandbox and FortiSandbox Cloud releases from 4.4.0 through 5.2.1. Both were reported via responsible disclosure (Fortinet, TrendAI Research, watchTowr). Fixes are available (RL:O) and CVSS E:F suggests functional exploits exist; no in-the-wild exploitation is confirmed.
Do: Upgrade FortiSandbox and FortiSandbox Cloud/PaaS to the fixed releases referenced in FG-IR-26-185 and FG-IR-26-179 immediately, prioritising internet-exposed management interfaces; Restrict access to the FortiSandbox GUI and Fabric API to trusted management networks and disable direct internet exposure; Review logs for unauthenticated access to the GUI and Fabric API endpoints and rotate any Fabric API credentials/integration keys; If running FortiSandbox as part of a security stack (e.g., feeding FortiGate/FortiMail), verify integrity of sandbox verdicts and monitor for signs of tampering

### [critical] Microsoft: October 2026 Patch Tuesday fixes 1,413 CVEs incl. two zero-days, one actively exploited (CVE-2026-96951, CVE-2026-108398)
https://helix.ml/threat-watch/i/microsoft-october-2026-patch-tuesday-fixes-1-413-cves-incl-two-zero-days-one-actively-exploited-cve-2026-96951-cve-2026 · Vulnerabilities · patched · since 2026-10-13 · CVE-2026-102208, CVE-2026-102866, CVE-2026-108398, CVE-2026-21413, CVE-2026-70242, CVE-2026-96951
Microsoft's October 2026 Patch Tuesday, its largest update ever, fixes 1,413 CVEs (1,102 in Windows), including 80 critical flaws and two zero-days. CVE-2026-96951 (CVSS 8.8), a Windows Shell Mark-of-the-Web bypass under active exploitation (discovered by Anthropic's Claude AI), lets crafted files skip SmartScreen, Office Protected View, macro blocking and Smart App Control. CVE-2026-108398 (CVSS 8.8) is a .NET Framework untrusted search path enabling code execution inside WDAC-protected processes; no active exploitation confirmed. Also critical: Outlook Reading Pane RCE CVE-2026-70242 (CVSS 9.8) triggering via email preview without interaction, and SharePoint EoP CVE-2026-102866 (CVSS 8.1). Fixes are available in the October updates.
Do: Deploy Microsoft's October 2026 security updates immediately across all Windows endpoints and servers, prioritizing internet-facing and WDAC-protected systems; Patch Outlook against CVE-2026-70242 (CVSS 9.8) as a top priority given no user interaction is required; Patch SharePoint Server against CVE-2026-102866 and review token issuance/proof-token exposure; Update .NET Framework everywhere, especially WDAC-protected environments, and monitor for suspicious assembly loading; Harden against MOTW bypasses: don't rely solely on SmartScreen/Protected View/macros policy; consider blocking risky file types at mail gateway

### [high] Microsoft Windows Command Injection Vulnerability (CVE-2026-96951)
https://helix.ml/threat-watch/i/microsoft-windows-cve-2026-96951 · Vulnerabilities · patched · since 2026-10-13 · CVE-2026-96951
Microsoft Windows Shell contains a command injection vulnerability that allows an unauthorized attacker to bypass a security feature over a network. CISA added CVE-2026-96951 to its Known Exploited Vulnerabilities catalog on Oct 13, 2026, which means attackers are exploiting it in the wild.
Do: 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.; US federal agencies must remediate by Oct 16, 2026 (BOD 22-01); treat that as the outer limit.

### [medium] Sharecare data breach: 318K accounts exposed
https://helix.ml/threat-watch/i/sharecare-data-breach · Breaches · no-fix-needed · since 2026-10-12
In August 2026, the digital health company Sharecare was the target of a ShinyHunters "pay or leak" extortion campaign. The group subsequently published data it claimed was taken from Sharecare's systems, containing 318k unique email addresses. Most of the data consisted of B2B sales and marketing records with names, physical addresses, phone numbers, job titles and employers. The data also included a small number of Brazilian health insurance plan members, including dates of birth, genders, marital statuses and CPF numbers (Brazilian taxpayer identification numbers). Exposed data: dates of birth, email addresses, employers, genders, government issued ids, job titles, marital statuses, names, phone numbers, physical addresses. The breach dates from Aug 12, 2026; Have I Been Pwned loaded it on Oct 12, 2026.
Do: If you had a Sharecare account, change its password and the password of any other account that reused it.; Turn on multi-factor authentication wherever it is offered.; Check whether your addresses are in this breach at https://haveibeenpwned.com.; Expect targeted phishing that quotes the leaked details; verify any unexpected contact out of band.

Breach data from Have I Been Pwned (haveibeenpwned.com) is licensed CC BY 4.0. Vulnerability data from the CISA KEV catalog and NVD.