SecurityApplication security

Brotli CVE-2026-111497 is now on CISA's exploited list, and you probably run more copies than you think

A flaw in Google's Brotli decoder can turn a crafted compressed stream into a memory write, and CISA lists it as exploited. Here's where Brotli hides beyond Node.js, which versions fix it, and the patch order that catches bundled copies.

Cohash Security Practice October 2026 updated November 2026 15 min read 7 chapters 3-question check
part 14 of 47 · Platform releases, explained from scratch
01 Crafted brstream 02 Brotlidecoder 1.0.3 to 1.2.0 03 Memoryoverwritten 04 Patch andrebuild

the ideaThe bug lives in a shared decoder, so every copy needs patching.

after reading, you can
  • Find where Brotli actually sits in a stack, well beyond Node.js, down to Python wheels and firewalls
  • Match each product to its fixed build, and catch containers still running old code on a patched host
  • Plan the patch order so services that unpack data from strangers go first

BrotlidefinitionGoogle's compression format, the one behind Content-Encoding: br. Lots of software copies Google's C library for it instead of writing its own. is the compression code that unpacks a lot of web traffic, and CISA now lists a flaw in it as exploited. Anything that decodes Brotli with Google's library from 1.0.3 to 1.2.0 needs the fixed build. CISA's November 10 deadline for US federal agencies has now passed. Node.js is the best-known case, but the same decoder sits inside Python packages, .NET, proxies and some firewalls.

in plain wordsCritical: on CISA's exploited list

A bad compressed file can break the code that unpacks it, and that code is in more places than you think.

Websites and apps squeeze data before sending it and unpack it on arrival, and Brotli is one of the common ways to do that. Google's Brotli library had a bug in the unpacking step. Feed it a deliberately broken stream and it writes past the end of a small memory buffer. At best the program crashes. At worst, researchers showed, it runs code the attacker hid in the data. The library is copied into hundreds of products, so one fix upstream turns into dozens of separate updates downstream.

think of it like this

It's like a mailroom sorter nobody ever taught what a bad label looks like. When one turned up, it assumed more mail was on the way and kept stacking letters into a slot that holds eight, and the overflow jammed the controls next door. The patched sorter just sends that parcel back.

who should care
  • Teams running any Node.js line
  • Python and .NET apps that unpack Brotli
  • Envoy, Istio and other proxy users
  • Palo Alto firewalls inspecting traffic
  • Anyone shipping containers
  • Siemens Teamcenter, Opcenter and WinCC sites
chapter 01

Why it matters to you

Most patch news is about one product. This one is about a part that many products share, so the hard work is finding where it hides. A server you patched last week can still carry an old Brotli inside a Node binary, a Python wheel or a container image built in August.

9.2Critical, the CVSS 4.0 score from Google, the CVE's issuer
Nov 10CISA's due date for US federal agencies, set on October 27 and now passed
1.0.3–1.2.0Affected releases of Google's Brotli library
3Fixed lines: 1.0.10, 1.1.1 and 1.2.1, all released on October 21

CISA added the flaw to its Known Exploited Vulnerabilities catalog on October 27, which is where it lists bugs it has evidence of attacks against. CISA's own notes call Brotli an open-source component that could be used by different products, and that's the real warning. Palo Alto Networks says it isn't aware of any malicious exploitation, so read the KEVdefinitionCISA's list of flaws it has seen attacked. Once a bug is on it, US federal agencies get a deadline. It's a sensible list for anyone else to patch from first. listing as being about Brotli in general, not about any one vendor.

How bad it gets depends on what your software does with compressed data from outside. Imperva's red team ran their own code on the official Node.js 24.22.0 image for Linux arm64, using a Brotli body sent to Express and a Brotli response pulled in by fetch(). It took them several attempts. Red Hat says hardening such as ASLR makes code execution harder on its systems, though it still expects crashes.

how the attack worksWhere the old decoder went wrong, in four stepsThe Node.js advisory, Google's fix and Imperva's write-up all describe the same chain. Where the data comes in depends on your app: a request body, a response your code fetches, a file someone uploads.
  1. 01 Crafted compressed data

    Someone gets Brotli data in front of your software. Usually that's a request body, a response your app fetched, or an uploaded file.

  2. 02 An impossible block switch

    The stream asks the decoder to switch to a block type it never declared. A correct decoder would stop right there.

  3. 03 Read as 'need more input'

    The old code treated that as a pause and kept appending bytes to an eight-byte internal buffer, past its end.

  4. 04 Memory corrupted

    Nearby decoder data gets overwritten. That can crash the process, leak memory or, with work, run the attacker's code.

For engineers: the weakness is filed as CWE-252, an unchecked return value, leading to CWE-787, an out-of-bounds write. Before the fix, DecodeBlockTypeAndLength() returned a plain true or false, so callers couldn't tell a broken stream from one that had simply run out of input. The fast decode path threw the result away. Google's fix, commit 0ed4268 ("Detect and report invalid stream earlier"), makes the function return an error code and adds a new one, BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH, so decoding stops on both paths.

tableThe same bug gets different ratings. Patch by where untrusted data reaches the decoder, whatever the label says
WhoRatingWhy it differs
Google (CVE issuer), GitHub advisory9.2 Critical (CVSS 4.0)Network, no login, no user action, though an attack requirement is present
Node.jsHighRated for Node's bundled decoder
Microsoft (.NET)8.1 High (CVSS 3.1)Brotli decompression is off by default in ASP.NET Core and HttpClient
Red HatImportantHardening on RHEL makes reliable code execution harder
UbuntuMedium priorityUbuntu's own triage of the brotli package
Palo Alto Networks9.2 Critical, urgency moderateOnly firewalls with Brotli inspection and TLS decryption turned on

Don't let a medium label on a Linux package slow you down. A researcher on the oss-security mailing list warned on October 23 that people might read the Node.js advisory and decide they had nothing to worry about because they don't run Node. He also questioned Ubuntu's medium rating. The library is the problem, and it's in a lot of places.

chapter 02

What got fixed, and where the fix has to land

Google released three fixed builds on the same day, one for each 1.x line people still use, so nobody has to move to a newer line. The hard part is that most of your software doesn't use Google's build directly. Each product that copied Brotli in has to ship its own update, and you have to install each one.

Where the fix has shipped so far

fixedGoogle Brotli 1.0.10, 1.1.1 and 1.2.1

The library itself, released October 21. Anything built from 1.0.3 to 1.2.0 needs one of these, or a vendor build that includes the change.

fixedNode.js 22.23.4, 24.22.1 and 26.12.1

Official Node.js builds bundle their own Brotli, so the system library doesn't help them. Older Node lines are end of life and get nothing.

fixedPython Brotli 1.2.1 and brotlicffi 1.2.1.0

Both PyPI packages compile the same C decoder. requests, aiohttp and other clients use them on their own whenever they're installed.

fixed.NET 8.0.33, 9.0.22 and 10.0.14

Also 11.0 RC3. Apps are exposed only if they turn on Brotli decompression or call BrotliStream or BrotliDecoder on outside data. .NET Framework isn't affected.

fixedEnvoy 1.40.0, 1.39.3, 1.38.6, 1.37.8, 1.36.12

Only deployments with the Brotli decompressor configured are exposed. Istio and other Envoy-based meshes pick it up through their own releases.

fixedPAN-OS hotfixes on 11.2, 12.1 and 12.2

Firewalls are exposed only with Brotli inspection and TLS decryption on, and inspection is off by default from 11.2.4. Palo Alto says the management interface isn't affected.

fixedLinux distribution packages

Ubuntu 22.04, 24.04 and 26.04, Debian 12 and 13 and Red Hat have patched libbrotli. Programs that link it still need a restart.

changedIdira SaaS remediated by Palo Alto

If you're on Idira SaaS, the old CyberArk cloud services, Palo Alto patched it for you and there's nothing to do. Idira Identity, IGA, Session Monitoring and Recording, SIA Database and Secure AI Agents are all on its remediated list. Self-hosted Idira isn't affected, it says.

fixedRed Hat OpenShift, most 4.x lines

Fixed CoreOS images shipped between November 6 and 11 for 4.13, 4.14, 4.17 and 4.19 to 4.22. Red Hat still lists OpenShift 5 as affected. Nodes only pick up the fix after the update rolls through and they reboot.

fixedPHP Windows builds 8.2 to 8.5

The October 26 rebuilds, 8.5.12-1, 8.4.27-1, 8.3.36-1 and 8.2.35-1, carry Brotli 1.2.1. The PHP team says the hole can be reached through cURL when automatic response decompression is on, which cURL leaves off by default.

fixedBeyondTrust Cloud Resource Broker

Version 25.3.64.30001, from November 4, moves the bundled .NET runtime to 8.0.33. BeyondTrust recommends a restart after the update.

changedSiemens Teamcenter, Opcenter and WinCC

No fix yet for Teamcenter, Opcenter or most WinCC products, though WinCC OA V3.20 is fixed in P17.1. Siemens lists mitigations: its Teamcenter knowledge-base steps, filtering on the IIS reverse proxy for Opcenter, and turning Brotli off where it isn't needed.

tableFixed versions by product. Anything older than the version in the middle column still has the flaw
What you runFixed inWatch out for
Google Brotli C library1.0.10, 1.1.1 or 1.2.1Vendored copies inside other projects need their own update
Node.js 22 / 24 / 2622.23.4 / 24.22.1 / 26.12.1Node 20 and older lines get no fix. Check node -p process.versions.brotli
Python Brotli / brotlicffi (PyPI)1.2.1 / 1.2.1.0Update the lockfile too, or the next build reinstalls the old one
.NET 8 / 9 / 108.0.33 / 9.0.22 / 10.0.14Self-contained and NativeAOT apps need a rebuild, not only a runtime install
Envoy1.40.0, 1.39.3, 1.38.6, 1.37.8 or 1.36.12Only matters if the Brotli decompressor filter is configured
PAN-OS 12.2 / 12.112.2.4-h1 / 12.1.4-h13, 12.1.7-h11, 12.1.10-h3All listed hotfixes were out by October 29. PAN-OS 11.1 and 10.2 aren't affected
PAN-OS 11.211.2.4-h23, 11.2.7-h23, 11.2.10-h17, 11.2.13-h4, 11.2.16-h111.2.10-h16 fixes PHP2Shell only. You need -h17 for Brotli
Ubuntu libbrotli24.04: 1.1.0-2ubuntu0.1, 22.04: 1.0.9-2ubuntu0.120.04 and older still said 'needs evaluation' on October 28
Debian libbrotli12: 1.0.9-2+deb12u1, 13: 1.1.0-2+deb13u1Debian says its nodejs packages use the system library and rates them unimportant, so the libbrotli update is the fix
Red Hat OpenShift 4.13, 4.14, 4.17, 4.19–4.22The CoreOS image from Red Hat's November 6–11 errata (4.22.22 for 4.22)OpenShift 5 and the RHEL 8 CoreOS image still showed as affected on November 16
PHP for Windows 8.2–8.58.2.35-1, 8.3.36-1, 8.4.27-1 or 8.5.12-1Same PHP version number, so check the -1 build suffix
BeyondTrust Cloud Resource Broker25.3.64.30001Restart after the update
Oracle PeopleSoft PeopleTools 8.61–8.63The PeopleTools patch in Oracle's November 2026 security patch updateOracle lists it under PeopleTools, in the Node.js behind OpenSearch Dashboards. Older releases are likely affected too
Oracle Communications DSR 9.0–9.3 / Unified Assurance 6.1.1–7.0.0Oracle's November 2026 security patch updateIn DSR it's the PMAC component. Oracle rates both 9.8
Siemens Teamcenter V2412, V2506, V2512, V2606No fix yetApply Siemens' Teamcenter mitigation steps now
Siemens Desigo CC V8 and V9Latest .NET updates via Windows UpdateFixed through the OS, not a Desigo release
Siemens Industrial Edge appsCloud Connector 1.24.3, Databus 4.0.1, Flow Creator 1.15.1 and othersCommon Configurator has no fix. Stop it on Edge devices; on IEM, uninstall the management apps and put IEM behind a firewall or WAF

From a quiet code change to the KEV list

  1. Feb 2026
    The code change enters Brotli

    The commit that becomes the fix is dated February 27, months before it was called a security fix. Some projects picked it up without knowing.

  2. Oct 21, 2026
    Brotli 1.0.10, 1.1.1, 1.2.1 and Node.js fixes
  3. Oct 22, 2026
    CVE out, PyPI Brotli and brotlicffi fixed
  4. Oct 23, 2026
    Envoy fixes; GitHub adds the PyPI packages
  5. Oct 25, 2026
    .NET 8.0.33, 9.0.22 and 10.0.14
  6. Oct 26, 2026
    Palo Alto confirms PAN-OS exposure

    Palo Alto lists affected versions with hotfix dates and an inspection workaround. The first hotfixes ship October 27.

  7. Oct 27, 2026
    CISA adds it to KEV
  8. Oct 29, 2026
    Last PAN-OS hotfixes ship
  9. Nov 6–11, 2026
    Fixed CoreOS for OpenShift 4.13, 4.14, 4.17 and 4.19–4.22
  10. Nov 10, 2026
    CISA's federal due date; Siemens lists Teamcenter

    On the day the federal deadline fell, Siemens published two advisories covering Teamcenter, Opcenter, WinCC and other software, most of it with no fix yet.

The February date explains something odd in the vendor lists. A few projects, MuPDF according to an independent tracker and Ghostscript according to a post on oss-security, pulled in the change before anyone knew it mattered, so their recent builds were fixed early. Others still bundle the old decoder. That tracker listed DuckDB, the bundled Apache Arrow build, p7zip and 7-Zip-zstd as unpatched on October 27, mostly through Parquet files and archives a user opens.

Two big vendors haven't finished checking. Cisco's advisory was still marked interim on November 13. Its fixed-release list includes Duo Network Gateway 3.4.2 and the Duo Authentication Proxy Local Manager for Windows 6.8.1, the second one due in November. Catalyst Center is still under investigation. Cisco says ISE, IOS XE and its Secure Firewall ASA and Threat Defense software aren't impacted. Fortinet updated its page on November 16 and still has FortiPAM, FortiEDR, FortiSandbox PaaS and FortiSwitch under investigation. Fortinet says FortiOS, FortiManager and FortiAuthenticator aren't impacted. On the identity side, Red Hat lists its build of Keycloak as not affected.

Oracle published its fix on November 17. Its monthly patch update lists the flaw three times, each scored 9.8 under CVSS 3.1 and each open over HTTP to someone who hasn't signed in. For PeopleSoft, the exposed piece is the Node.js runtime that OpenSearch Dashboards uses in PeopleTools 8.61 to 8.63, the supported versions Oracle checked. Oracle thinks older releases probably have it too. You fix it with the PeopleTools patch, and Oracle's patch availability note says which one. The other two entries are the PMAC component of Oracle Communications Diameter Signaling Router 9.0 to 9.3 and the core of Oracle Communications Unified Assurance 6.1.1 to 7.0.0. Oracle's next patch date is December 15.

Plant and engineering teams should read the Siemens advisories closely, because they don't fit the usual patch-and-restart routine. Siemens gives Teamcenter, Opcenter and the PADS and Xpedition tools a CVSS 3.1 score of 9.8 and has no fixed release for any of them yet. For Teamcenter it points to manual mitigation steps in a support article. For Opcenter, the place to mitigate is the IIS reverse proxy in front of it. For the design tools it says to turn Brotli compression off and block it at the network firewall. Industrial Edge is different again: if no management applications are installed, Siemens says nothing is needed, since the library ships but isn't used. Sites running device apps still need the mitigations.

Some paths are easy to miss. A researcher on oss-security pointed out on October 26 that git's HTTPS transport is exposed too, when libcurl is built with Brotli support, which he says most distributions do. So a build server cloning from a hostile mirror counts. On those systems the distribution's libbrotli update covers git, once nothing still has the old library loaded.

chapter 03

What to do now

What to do now, by who you are

Business ownertoday
  • Ask IT for a list of systems that unpack outside data with Brotli, and a patch date for each one.
  • Ask your hosting, SaaS and firewall vendors for their CVE-2026-111497 status in writing.
  • If you sell to US federal agencies, expect to be asked whether you met the November 10 date. Have the answer in writing.
  • Ask who checks the logs afterwards. Patching closes the gap but says nothing about last week.
IT and operationsthis week
  • Update libbrotli from your distribution, then restart everything that has it loaded.
  • Move Node.js to 22.23.4, 24.22.1 or 26.12.1 on servers, build agents and serverless runtimes.
  • Check Palo Alto firewalls with show system setting brotli. Where inspection is on, hotfix them or switch it off for now.
  • Proxies that decode br come before internal systems. Envoy needs its own release, and so does a mesh built on it.
  • If you run Siemens Teamcenter or Opcenter, apply Siemens' mitigation steps now. There's no patch to wait for yet.
Developersthis week
  • Search lockfiles for Brotli and brotlicffi, raise them to 1.2.1 and 1.2.1.0, and regenerate the lock.
  • Move .NET to 8.0.33, 9.0.22 or 10.0.14, and rebuild self-contained and NativeAOT apps.
  • Rebuild every container image on a patched base. A new tag on an old base changes nothing.
  • Find code that unpacks Brotli it didn't create: fetch() responses, request bodies, uploads, queue messages.
Security teamnow
  • Treat this as a component hunt. Search SBOMs and image scans for brotli, libbrotlidec and brotlicffi.
  • Don't trust a quiet scanner. Early on, Python scanners missed the PyPI packages, and vendored copies rarely show.
  • Look for decoder crashes and unexpected restarts in Node, Python and proxy processes since October 21.
  • Track vendor statements for appliances and SaaS you can't patch yourself. Cisco and Fortinet were still investigating parts of their range on November 16.

If you only have an hour, start with services that unpack data from the internet: public APIs that accept compressed bodies, crawlers and link previewers, webhooks and anything that imports from a URL. Imperva showed both directions work, data coming in and data your app goes out and fetches. A WAF can catch the first one. Nothing in front of your app sees the second.

find-brotli (example commands)example output
# example output, with made-up versions. Run these on every host and inside every image, because each can differ
node -p "process.version + ' brotli ' + process.versions.brotli"   # Node's own copy, which is the one that counts
v24.22.0 brotli 1.2.0
pip show Brotli brotlicffi | grep -E 'Name|Version'   # run it in each virtualenv, since they don't share packages
Name: Brotli  Version: 1.2.0
dpkg -l | grep -i brotli
ii  libbrotli1:amd64  1.1.0-2ubuntu0.1
sudo grep -l brotlidec /proc/*/maps 2>/dev/null
/proc/2214/maps
# The package is patched but process 2214 still has the old library loaded. Restart it

A patch order that covers the hidden copies

  1. 01
    Build the list

    Pull every place Brotli lives: distribution packages, Node versions, Python lockfiles, .NET runtimes, proxies, firewalls and container images. SBOMs help, but check images directly too.

  2. 02
    Rank by who sends the data

    Anything that unpacks data from the internet or from partners goes first. Internal batch jobs on trusted files can follow.

  3. 03
    Shrink exposure while you wait

    Reject Content-Encoding: br request bodies at the proxy or WAF where your apps don't need them. On PAN-OS, disable Brotli inspection until the hotfix is in.

  4. 04
    Patch and restart

    Update the library or runtime, then restart processes and rebuild images. Pin the new versions in lockfiles and Dockerfiles so the next build doesn't undo it.

  5. 05
    Prove it

    Read the version back from running processes and deployed images, not from the change ticket. Record the result against each system on the list.

chapter 04

Harden so the next one hurts less

This bug is a preview of how shared components fail. The flaw sat in one C file, and the fix took a week to reach a handful of big projects while others are still waiting. Teams that already knew where Brotli lived had a short week. Everyone else spent it searching.

before

Before: nobody knows where the decoder is

Old Brotli copies sit in images nobody has rebuilt in months. The app unpacks whatever it's sent or fetches, and nobody checks.

Before: nobody knows where the decoder is Old Brotli copies sit in images nobody has rebuilt in months. The app unpacks whatever it's sent or fetches, and nobody checks. 01 · INTERNET 02 · EDGE 03 · APP br request unchecked fetches br reply full access Partner or attacker sends br data Proxy passes br bodies through Node or Python service old bundled Brotli Broad service account reads every table © Cohash · cohash.com
01 · INTERNET02 · EDGE03 · APP Partner or attacker: sends br data Partner or attacker sends br data Proxy: passes br bodies through Proxy passes br bodies through Node or Python service: old bundled Brotli Node or Pythonservice old bundled Brotli Broad service account: reads every table Broad serviceaccount reads every table br request unchecked fetches br reply © Cohash · cohash.com
after

After: known, pinned and contained

Someone can find every Brotli copy from the SBOM. The edge drops compressed bodies on routes that don't need them, and the service only reads its own tables.

After: known, pinned and contained Someone can find every Brotli copy from the SBOM. The edge drops compressed bodies on routes that don't need them, and the service only reads its own tables. 01 · EDGE 02 · BUILD 03 · APP filtered blocks old images least privilege WAF or proxy br bodies only where needed SBOM and image scan flags old Brotli Service on pinned runtime Node 24.22.1 Scoped identity own data only © Cohash · cohash.com
01 · EDGE02 · BUILD03 · APP WAF or proxy: br bodies only where needed WAF or proxy br bodies only where needed SBOM and image scan: flags old Brotli SBOM and image scan flags old Brotli Service on pinned runtime: Node 24.22.1 Service onpinned runtime Node 24.22.1 Scoped identity: own data only Scoped identity own data only filtered blocks old images © Cohash · cohash.com
side by sideThe same stack, run two ways. The right-hand column turns the next shared-library CVE into a search query
Usual setup
  • No SBOM, so finding Brotli means asking every team
  • Base images rebuilt when someone remembers
  • Lockfiles float, so a rebuild can pull an old wheel back in
  • The app's service account can read far more than the app needs
Hardened setup
  • Ask 'where do we run Brotli?' and someone answers from the SBOM in minutes
  • Someone rebuilds base images every month, and again the day a bad CVE lands
  • Pinned runtimes and lockfiles, updated by pull request
  • Each service has its own login and only sees its own tables. One bad request can't reach the rest
  • The edge only accepts compressed request bodies on routes that need them

Two of these do most of the work. An SBOMdefinitionA software bill of materials: a list of the components inside an application or image. It lets you search for a library like Brotli instead of asking every team. you can search turns 'are we affected?' from a week of emails into an afternoon. A scoped identity limits what an attacker gets if a decoder bug does turn into code execution, because the process can only reach what it was meant to. Our post on the PHP2Shell and Node.js releases walks through scoping the app account in more detail.

chapter 05

If you've been breached

If you find signs someone used this

Nobody has published indicators of compromise for this flaw. Imperva suggests treating decoder errors and unexpected process exits as leads to check, not proof. Work in order and keep evidence before you change anything.

  1. 01Containfirst hour
    • Take the suspect service out of rotation and snapshot the host or container before restarting it.
    • Block its outbound traffic except to what the investigation needs.
    • Copy logs off the box: application, proxy, WAF and crash or core dumps.
  2. 02Investigatefirst days
    • Line up crashes in Node, Python, .NET or proxy processes since October 21 with the requests or fetches just before them.
    • Look for child processes, new files or outbound connections from the service that nobody can explain.
    • Check what the service's credentials did: database queries, cloud API calls and secret reads.
  3. 03Rebuilddays 1 to 3
    • Rebuild hosts and images on patched versions instead of cleaning them in place.
    • Redeploy from source you trust. Pin the lockfiles to fixed Brotli versions first, or the rebuild just brings the old one back.
  4. 04Rotateafter rebuild
    • Change every secret the process could read. That usually means API keys, database passwords, tokens and signing keys.
    • Do it after the rebuild, so an attacker still inside can't read the new values.
  5. 05Report and learnfirst weeks
    • Bring in legal early. Breach notice rules depend on the data and your state or sector.
    • Ring the insurer early and ask what the policy needs from you before anyone hires outside help. Customers hear from you once you know their data was reachable.
    • Add the gaps you found to the SBOM and patch process.

Memory bugs leave little behind. A crash in a decoder can be a failed attempt or a broken file from a partner, and a successful attempt might not crash anything. That's why the rotation step matters even when the evidence is thin.

chapter 06

What this could look like: three typical setups

What this could look like: three typical setups

01 br requestbody 02 Ingress passes it on 03 Node 24.22.0pod bundled Brotli 04 Rebuilt on24.22.1
scenario 01High risk
A retailer's API on Node.js in containers
the setup
A retailer's order API runs on Node 24.22.0 in Kubernetes and takes compressed JSON from partners through Express 5. Ops patched the host OS on Monday and closed the ticket.
what happens
The host patch did nothing for the app. Node bundles its own Brotli, so every pod still runs the old decoder, and any partner or attacker who can post to the API can reach it.
what to do
Rebuild the image on node:24.22.1, roll the pods and check process.versions.brotli in each one. Until then, reject br bodies at the ingress on routes that don't need them.
01 Crawler requests, aiohttp 02 Hostile site br response 03 Brotli 1.2.0 04 Brotli 1.2.1
scenario 02Medium risk
A data team's Python crawler
the setup
A research team runs a Python crawler on requests and aiohttp that pulls pages from thousands of sites. Brotli 1.2.0 came in as a dependency, and nobody imports it directly.
what happens
Any site the crawler visits can send a Brotli response, and the HTTP client unpacks it on its own. A WAF in front of the crawler never sees this traffic, because the crawler started the request.
what to do
Raise Brotli to 1.2.1 in the lockfile and rebuild. If that has to wait, uninstall Brotli so the clients fall back to gzip, and remove any extra that would pull it back in.
01 Web page br content 02 PAN-OSdataplane decrypt + inspect 03 Inspectionoff 04 User
scenario 03High risk
A bank with TLS inspection on PAN-OS
the setup
A bank decrypts outbound web traffic on PA-Series firewalls running PAN-OS 11.2.10-h16, with Brotli inspection turned on so the firewall can scan compressed pages.
what happens
The firewall unpacks Brotli from any website a user visits, so the box doing the inspecting is the one exposed. The team thought -h16 covered it, but that hotfix only fixes PHP2Shell.
what to do
Move to 11.2.10-h17. Until then, run set system setting brotli-encoding disable and confirm show system setting brotli says Enabled: no.

These three are made up, and none is a real incident or a Cohash client. Each version number in them comes from the vendor pages behind this post.

chapter 07

How Cohash helps

We help teams find shared components like Brotli across images, runtimes and appliances, patch them in an order that keeps services up, and scope the identities those services run under. Our DevSecOps practice handles SBOMs and image rebuild pipelines, and our network security team works on firewall inspection settings. If you'd like a second pair of eyes on your exposure, start with an assessment.

key takeaways

What to take from this

  1. 01

    The flaw is in Google's Brotli library, so it reaches well past Node.js. Check Python, .NET, proxies and firewalls too.

  2. 02

    Fixed library lines are 1.0.10, 1.1.1 and 1.2.1. Products that bundle Brotli need their own update.

  3. 03

    Restart processes and rebuild images after patching. An installed package doesn't fix a running service.

  4. 04

    Patch whatever unpacks outside data first. Responses your own code fetches count, and a WAF won't see those.

  5. 05

    On PAN-OS, 11.2.10-h16 isn't enough. Hotfix or turn off Brotli inspection.

  6. 06

    Siemens Teamcenter and Opcenter have no fix yet. Put Siemens' mitigations in place now.

  7. 07

    Keep a searchable SBOM, so the next shared-library CVE takes an afternoon to scope.

platforms in this noteCyberArk →Oracle PeopleSoft →
fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers CyberArk: scope, roles and architecture
  2. How Cohash delivers Oracle PeopleSoft: scope, roles and architecture
  3. Hire vetted CyberArk engineers
  4. DevSecOps
  5. Book a 30-minute working session with a senior engineer
01Am I affected by CVE-2026-111497?

You are if anything you run decodes Brotli with Google's library from 1.0.3 to 1.2.0, or a product that bundles it, on data someone else controls. Common cases are Node.js 22, 24 and 26 before the October fixes and end-of-life lines such as 20, 23 and 25, Python apps with Brotli or brotlicffi installed, .NET apps that turned on Brotli decompression, Envoy with the Brotli decompressor, and some PAN-OS firewalls.

02I don't use Node.js. Do I need to care?

Yes. The bug sits in Google's Brotli library, and Node.js just happens to be the best-known product that bundles it. The fixed-versions table above lists the others we checked. Search your inventory for Brotli itself, because the Node advisory won't tell you about the rest.

03Is PeopleSoft affected by CVE-2026-111497?

It is, through PeopleTools. In the patch update Oracle put out on November 17, PeopleTools 8.61 to 8.63 show up as affected, because the Node.js that runs OpenSearch Dashboards carries the bug. Oracle scores it 9.8. Install the PeopleTools patch from that update. Two Oracle Communications products, Diameter Signaling Router and Unified Assurance, are on the same list.

04Is CVE-2026-111497 being exploited?

CISA thinks so. It added the flaw to its Known Exploited Vulnerabilities catalog on October 27 with a federal due date of November 10, which has now passed. Palo Alto says it isn't aware of any malicious exploitation. Imperva has shown code execution on an official Node.js build, though it took several attempts.

05Which version fixes it?

It depends on what you run, and the fixed-versions table above has the full list. The library itself is fixed in 1.0.10, 1.1.1 and 1.2.1, and Node.js in 22.23.4, 24.22.1 and 26.12.1. For anything else, go by the vendor's own advisory, since each one ships its own build.

06We run Siemens Teamcenter. Is it affected, and is there a patch yet?

Yes. Siemens' November 10 advisory lists Teamcenter V2412, V2506, V2512 and V2606 as affected, with a CVSS 3.1 score of 9.8 and no fix yet. Siemens points to manual mitigation steps in a Teamcenter support article. Opcenter, Simcenter Studio and the Xpedition tools are in the same advisory, also without fixes.

07Is OpenShift fixed for the Brotli flaw?

Mostly. Red Hat shipped fixed CoreOS images for OpenShift 4.13, 4.14, 4.17 and 4.19 to 4.22 between November 6 and 11, including 4.22.22. Its CVE page still lists OpenShift 5 and the RHEL 8 CoreOS image as affected. Nodes are fixed only after the update rolls out and they reboot.

08I updated the package, but the scanner still flags it. What did I miss?

Running processes keep the old library until they restart, and container images keep whatever they were built with. Restart services, rebuild images on a patched base, and update lockfiles so the next build doesn't pull the old version back in.

09Is there a workaround if I can't patch yet?

Partly. You can reject Brotli request bodies at a proxy or WAF, uninstall the Python Brotli packages so clients fall back to gzip, remove Brotli from .NET decompression settings, or turn off Brotli inspection on PAN-OS. None of these covers every path, and Node.js lists no workaround, so plan to patch.

10Are browsers affected?

Chromium and Firefox were reported fixed before the public list of affected projects was made. Keep browsers on automatic updates and check managed fleets that pin old versions.

up next in this track

Keep the thread going.

What shipped, what changed underneath, and what it means for your upgrade.

  1. 01HashiCorp Vault 2.2 explained: TPM login, post-quantum PKI and the October fixes
  2. 02Upgrading to SailPoint IdentityIQ 9.0: what breaks and what to fix first
  3. 03Terraform 1.17 explained: what's new, who it touches and how we'd upgrade
  4. 04BeyondTrust Remote Support zero-day: patch it, then check who got in
  5. 05Patch PHP and Node.js this week: what broke and who's exposed
  6. 06OpenShift support dates through 2027: which clusters run out first and how to plan the upgrades
  7. 07Oracle's October security patches: what to fix first in EBS, PeopleSoft and Access Manager
  8. 08Oracle's eMudhra alert now covers Database Server: patch, then test what breaks
  9. 09Delinea Secret Server auth bypass: why the FIDO2 hotfix isn't enough
  10. 10IBM Verify Access flaws let attackers run code without a login: patch to 11.0.3.2
  11. 11Foundry Workflows retire on December 1. We'd start moving yours to Agent Framework now
  12. 12Vertex AI is retiring text-embedding-005 and three other embedding models: how to re-embed before search breaks
  13. 13dbt drops v1.3 to v1.7 from its platform on January 31, 2027: get pinned jobs onto a release track before they're deleted
  14. 14Brotli CVE-2026-111497 is now on CISA's exploited list, and you probably run more copies than you think
  15. 15Auth0 moved the Rules and Hooks deadline: Hooks stop on 30 April 2027, Rules on 31 January 2028
  16. 16Still on Okta Classic Engine? Three features stop working on March 5, 2027, and two of them block the upgrade
  17. 17Patched GitLab, still exposed: the CI regex bug CISA lists as exploited, and the Ruby step people miss
  18. 18Patched Ivanti Connect Secure in October? Two more exploited bugs, and the AD cleanup
  19. 19Patch roundup, week of Oct 26: upgrade Secret Server today, then work down the list
  20. 20UiPath 2023.10 support has run out and 2024.10 is next. What we'd upgrade first
  21. 21Password Safe 24.3 runs out of support in December, and 26.3 is still one upgrade away
  22. 22Upgrade Entra Connect Sync before April 2027 and move users off Microsoft's SMS codes
  23. 23Chrome drops XSLT on 17 November. What breaks in InterSystems, and the fix for your version
  24. 24Agent Builder, Evals and saved prompts shut on 30 November. Here's what to pull out first
  25. 25BeyondTrust Remote Support and PRA 24.3 lose support in November, and there's no one-step upgrade
  26. 26OpenShift 4.19 is running out of support. Do you park on 4.22 or keep going to 5.0?
  27. 27Terraform Enterprise 2.1 moves VCS ingress into your agents. What to change before October 2027
  28. 28Mule 4.12 Edge leaves standard support this month. Upgrade to 4.13 before CloudHub does it for you
  29. 29RSA SecurID primary support ends in stages from December. Here's how you get to 8.9
  30. 30Delinea Secret Server login bypass: why 12.2.7 won't save you from this 9.9
  31. 31Entra password reset won't take directory phone numbers from February 2027. Who gets stuck?
  32. 32Linux kernel CVE-2026-98432: why switching off MPTCP won't save you, and what to patch
  33. 33Patch roundup, week of Nov 2: fix Linux and WS_FTP first, then work down the list
  34. 34Auth0's lazy migration changes on 20 January 2027, and half-imported users won't fix themselves
  35. 35Your Databricks AI Functions need Runtime 17.3 LTS by January 2027, even if 15.4 is still supported
  36. 36SonicWall's SSL VPN bug lets a valid password skip SAML and your MFA
  37. 37Oversized Auth0 profiles can break logins after 4 March 2027. Here's how to find yours
  38. 38You patched your Cisco email gateway. One email can still take it over.
  39. 39Barracuda email gateways are being hacked through their admin page: patch and lock it down
  40. 40Citrix NetScaler's November fixes: one flaw hits every box, and Console has a login bypass
  41. 41Fortinet's November fixes: FortiMail, FortiManager and FortiAuthenticator flaws that need no login
  42. 42November's Microsoft patches: do the domain controllers and Outlook first
  43. 43SAP's November patches: four flaws that need no password
  44. 44GitLab's off-cycle Git fix: a merge request can run code on Gitaly, and source installs need two patches
  45. 45Auth0 is pulling Node 18 out from under your login code. Here's how to move it to Node 22
  46. 46Attackers are using an Apache Axis 1 flaw, and Apache doesn't plan a fixed release
  47. 47Oracle's November security patches: Access Manager and WebLogic 10.0s, plus Java4Shell
all learning tracks →
Coderead-only Old: 18 Nov2026 Hooks stop Rules stop Nov 2024 Jan 2028
Security · 14 minAuth0 moved the Rules and Hooks deadline: Hooks stop on 30 April 2027, Rules on 31 January 2028

Two dates now, not one. Hooks go first, Rules nine months later.

read next
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it