Skip to content
Zero Day Playbook

Dependency playbook: the first 72 hours when a library you ship has a critical flaw

  • 0 to 4 hours: 4 steps
  • 4 to 24 hours: 3 steps
  • 24 to 72 hours: 3 steps
  • Hours elapsed: the bar under the cells

Checklist to print

  1. 0 to 4 hours4 steps, due by hour 4
    1. 1

      Application owner, hand-off

      Write down four facts from the advisory before you search: the package coordinates as a package URL (for example pkg:pypi/brotli), the affected range, the fixed versions, and the trigger condition. For CVE-2026-111497 these are Brotli 1.0.3 up to but excluding 1.0.10, 1.1.0 up to but excluding 1.1.1 and 1.2.0 up to but excluding 1.2.1, fixed in 1.0.10, 1.1.1 and 1.2.1, and Node.js 22.x before 22.23.4, 24.x before 24.22.1 and 26.x before 26.12.1. Node.js lines 20.x, 23.x and 25.x are end-of-life and get no fix. The trigger is decompressing Brotli data an attacker can influence. Also note that the package may be bundled in a runtime rather than installed as a package: here Node.js carries its own copy.

      Done at

    2. 2

      Application owner, hand-off

      Query your SBOM store for both the package and any runtime that bundles it. For CycloneDX files on disk: jq -r '.components[]? | select(.name|test("brotli";"i")) | [.name, .version, .purl] | @tsv' bom.json, run in a loop over every file. For Dependency-Track: curl -s -H "X-Api-Key: $KEY" "$DT/api/v1/component/identity?name=brotli". Repeat both with name node and keep the versions below 22.23.4, 24.22.1 and 26.12.1. A generated SBOM for an image is also queryable: syft <image> -o cyclonedx-json | jq ... . Expect the runtime query to carry the real hits, because the bundled decoder is not a component of its own.

      Done at

    3. 3

      Application owner, hand-off

      For services without a current SBOM, ask the package manager for the dependency path. npm ls --all | grep -i brotli and, for the inbound paths, npm ls express body-parser. Python: pip show brotli brotlicffi and pipdeptree -r -p brotli. Maven: mvn dependency:tree -Dincludes=org.brotli. Gradle: gradle dependencies --configuration runtimeClasspath | grep -i brotli. Go: go mod graph | grep -i brotli and go version -m ./bin/app | grep -i brotli. Ruby: bundle info brotli. Runtime: node --version on hosts and CI runners, docker run --rm <image> node --version for images, and ldd $(command -v node) | grep -i brotli to see whether Node.js links the system library, then dpkg -l | grep -i brotli, rpm -q brotli or apk info -v | grep brotli. Do not test process.versions.brotli: ELLIO reports it shows 1.2.0 on patched and vulnerable builds alike.

      Done at

    4. 4

      Application owner, hand-off

      Decide reachability for each hit, using the three paths into the decoder. Inbound bodies: Express 5, body-parser 2.x and Koa with @koa/bodyparser inflate Brotli request bodies before route handlers run, while a bare node:http server does not. Outbound responses: built-in fetch(), undici, axios, got and SuperAgent decode Brotli responses, so webhooks, link previews and crawlers that fetch URLs a user supplies count. Direct calls: grep -rn "brotliDecompress\|createBrotliDecompress" . in your code and in node_modules. Then test one staging service: POST a corrupt body (not Brotli) with the header Content-Encoding: br. A 400 from the framework before your handler runs usually means a decoder ran on the body.

      Done at

  2. 4 to 24 hours3 steps, due by hour 24
    1. 5

      Application owner, hand-off

      Move each reachable service to the fixed version, including the dependencies you do not declare. For a runtime, change the pinned base: a Dockerfile pinned to node:24.22.0 or node:22.23.3 stays vulnerable until the pin moves. For a transitive package, force it from your own manifest: npm overrides in package.json, yarn resolutions, a Maven dependencyManagement entry, a pip constraints file passed with -c, or go get <module>@<fixed>. Python Brotli moves to 1.2.1 and brotlicffi to 1.2.1.0. Open one pull request per repository and run the suite. A Node.js upgrade fixes only the copy Node.js bundles, so rerun step 3 after the change.

      Done at

    2. 6

      Application owner, hand-off

      Give platform engineering the smoke tests and the rollback criteria before they deploy. For a decoder fix, the tests are: a valid Brotli request body decodes to the same content as before; a Brotli response from a stub upstream decodes through your fetch client; and a corrupt body is rejected with a 400 and does not crash the worker. Rollback criteria: crash-loop restarts, or a jump in 400 responses on requests with Content-Encoding br beyond what the corrupt-body test produces. A patched decoder rejects a malicious body with ERR__ERROR_FORMAT_BLOCK_SWITCH (decoder error code -17), so that string in logs is expected after the change.

      Done at

    3. 7

      Application owner, hand-off

      For services that cannot move yet, ask platform engineering for the inbound stopgap at the proxy and confirm it with a request. In nginx: if ($http_content_encoding ~* "\bbr\b") { return 415; } in the server block, then curl -s -o /dev/null -w '%{http_code}\n' -H 'Content-Encoding: br' --data-binary @bad.bin https://staging.example/api should print 415. Aikido and ELLIO give this stopgap because the Node.js advisory lists no workaround. It does not cover Brotli responses your own service fetches. For those, disable or restrict features that fetch user-supplied URLs until the upgrade ships.

      Done at

  3. 24 to 72 hours3 steps, due by hour 72
    1. 8

      Application owner, hand-off

      Check the built artifacts, not the repositories. For every production image run docker run --rm <image> node --version and compare with 22.23.4, 24.22.1 and 26.12.1, and rerun the SBOM and pip show queries against what is deployed. Do not accept a scanner's Brotli finding or silence as the proof for Node.js: the version printed by the image is the proof.

      Done at

    2. 9

      Application owner, hand-off

      Look back through the exposure window for attempts and for crashes. Search application logs for ERR__ERROR_FORMAT_BLOCK_SWITCH, which marks a failed attack against a patched build. On vulnerable builds look for repeated worker crashes, restarts and requests with Content-Encoding br just before them, and check /var/lib/systemd/coredump: ELLIO notes a crash core file can hold credentials from other users' sessions, so restrict who can read it and how long you keep it. Some other decoders (Python Brotli 1.2.0, brotlicffi 1.2.0.0) return no bytes, never finish and raise no error, so look for stuck requests with CPU at 100 percent too. If a vulnerable, internet-reachable service saw this traffic or unexplained crashes, treat the host as possibly compromised and start your incident process.

      Done at

    3. 10

      Application owner, hand-off

      Make the old range fail the build. Add a CI step that reads the runtime version and exits nonzero below the fixed release of its line: v=$(node -p process.versions.node); case $v in 22.*) m=22.23.4;; 24.*) m=24.22.1;; 26.*) m=26.12.1;; *) exit 1;; esac; printf '%s\n%s\n' $m $v | sort -V -C || { echo old Node.js; exit 1; }. Add a lock-file check for the other packages, for example trivy fs --exit-code 1 --severity CRITICAL . on the repository. Keep the override from step 5 until the parent package ships the fix on its own.

      Done at

A dependency flaw is different from a flaw in a product you installed. Nobody on your team chose the vulnerable code, and it often does not appear in a manifest: the Brotli decoder behind CVE-2026-111497 is compiled into the Node.js binary, so no package file lists it. Attackers exploit these flaws through the data your application already accepts. In the Brotli case that was a request body sent with Content-Encoding br, or a compressed response fetched from a URL the attacker influences. What the attacker gains is code execution inside your service, with its credentials and network position.

The page is for the team that owns an application. It assumes you will not be told which of your services is affected. The hard parts are three. A fix released for the parent package may leave your copy untouched. The version string may not tell patched from vulnerable builds. And the owner has to prove, service by service, whether untrusted input reaches the decoder.

When no fix exists yet

Three kinds of dependency have no fix when you need one. The first is an end-of-life runtime line: Node.js 20.x, 23.x and 25.x get no release for CVE-2026-111497, so the only complete answer is a move to 22, 24 or 26. The second is a copy inside software you cannot rebuild: NVD lists many Siemens products as embedding Brotli, and the fix arrives when the vendor ships it. The third is a library with no release yet. The Brotli fix sat in the public master branch of google/brotli from 27 Feb 2026, eight months before a release carried it, so a snapshot build from the fix commit was possible. Its cost is a build nobody has tested and a copy you now maintain.

For services that stay on a vulnerable copy, the mitigations are the proxy rule for inbound Content-Encoding br, the platform edge rules where they exist (Vercel added them on 21 Oct 2026 for inbound requests only), and removing the features that fetch user-supplied URLs. Each costs a class of legitimate traffic or a feature. Take the service offline, or the feature off, when it decodes attacker-influenced data on a path you cannot filter and the copy cannot be replaced: CISA's KEV action for this CVE is to apply the vendor mitigations or stop using the product if none are available. A batch job that never reads untrusted compressed input can stay up with the exception recorded and dated.

CVE-2026-111497 worked through, hour by hour

The Brotli decoder flaw is a dependency case in its purest form. The vulnerable code was Google's Brotli, shipped inside Node.js, inside Python packages and inside other products. CISA lists it in the KEV catalog as Google Brotli Unchecked Return Value Vulnerability. NVD rates it CVSS 9.8. The Node.js project named the reporters and the fixed releases on 21 Oct 2026. The rows below start with the commit that carried the fix and end with the CISA due date.

WhenWhat happenedSource
27 Feb 2026The fix is committed to the public master branch of google/brotli with no release and no advisory, 236 days before the Node.js release.source
14 Oct 2026Node.js maintainers post a pre-alert on oss-security: new releases of Node.js 22, 24 and 26 on or shortly after 21 Oct, the highest severity being HIGH. It gives seven days to take the inventory of Node.js versions in steps 1 to 3.source
21 Oct 2026Node.js releases 22.23.4, 24.22.1 and 26.12.1 and publishes the advisory. Brotli 1.2.1 ships the same day, and 1.0.10 and 1.1.1 carry the fix too. Vercel adds firewall rules for inbound requests.source
22 Oct 2026NVD publishes the record and GitHub lists GHSA-9v8h-qqgm-4m35. A first public proof of concept appears. Aikido says it reached code execution only against a deliberately weakened test build.source
23 Oct 2026A post on oss-security points out that the flaw is in Google Brotli and reaches every consumer, and that Ubuntu rates it medium.source
25 Oct 2026ELLIO reports a scanner named node2shell-check mapping hosts that decompress Brotli, and reproduces code execution on default Node.js 24.22.0 on x86-64.source
26 Oct 2026, 15:08 UTCELLIO sensors record a Brotli-coded request body of 23,069,983 bytes, the first exploit traffic it reports.source
27 Oct 2026CISA adds the CVE to the KEV catalog with a due date of 10 Nov 2026.source

Count from the advisory on 21 Oct. The 72-hour window ends on 24 Oct, two days before the first exploit traffic ELLIO reports on 26 Oct and three days before the KEV entry. The pre-alert of 14 Oct named the release lines and the date, so the inventory of Node.js versions in use on lines 22, 24 and 26 could finish a week ahead of the first traffic. A team that relied on the SBOM alone would have missed the Node.js-bundled copy and the Dockerfile pins to node:24.22.0, which stay vulnerable after a base-image refresh. The NVD record lists Siemens products as embedding Brotli: for those, steps 5 to 7 end with a vendor ticket and the proxy rule, and the KEV due date of 10 Nov 2026 is the date the exception must close.

Sources

  1. Node.js security releases, 21 Oct 2026 (vendor advisory), read 19 Nov 2026
  2. CISA KEV entry for CVE-2026-111497, read 19 Nov 2026
  3. ELLIO research on Node2Shell exploitation and affected builds, read 19 Nov 2026
  4. Aikido analysis and fix guidance, read 19 Nov 2026
  5. Node.js security release pre-alert on oss-security, 14 Oct 2026, read 19 Nov 2026
  6. oss-security post, 23 Oct 2026, read 19 Nov 2026
  7. Google Brotli 1.2.1 release, read 19 Nov 2026
  8. NVD record for CVE-2026-111497, read 19 Nov 2026

Last reviewed 19 Nov 2026.