DE EN IT

~/exploited / cve-2026-111497

CVE-2026-111497: Google Brotli

According to CISA this vulnerability is already used in attacks (added on 27 October 2026).

Key facts

CVECVE-2026-111497
VendorGoogle — Brotli
VulnerabilityGoogle Brotli Unchecked Return Value Vulnerability
Added27 October 2026
Deadline (US agencies)10 November 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score9.2 (critical) · CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack over the network, complexity: low, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 82.64%. Higher than 99.7% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-252
CWE-787 — Out-of-bounds Write
Affected versionsbrotli: >= 1.0.3, < 1.0.10
brotli: >= 1.1.0, < 1.1.1
brotli: >= 1.2.0, < 1.2.1
node.js: < 22.23.4
node.js: >= 23.0.0, < 24.22.1
node.js: >= 25.0.0, < 26.12.1
brotlicffi: < 1.2.1.0
.net: >= 8.0.0, < 8.0.33
and 33 more

Description (NVD)

A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.

Description (CISA)

Google Brotli contains an unchecked return value vulnerability that allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether Google Brotli is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 27 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).