Futureweb

Security

CVE-2026-111497 is the Brotli decoder flaw Node already shipped a fix for. Bun's advisory and the NVD entry put the same identifier in other products.

CVE-2026-111497 is the Brotli decoder flaw. Node's fix is already filed. Bun says 1.4.4 updates the library. This page does not describe the trigger.

The short version

NVD describes a buffer overflow in the Brotli decoder and names fixed library lines 1.0.10, 1.1.1, and 1.2.1. Bun's advisory GHSA-663w-cv8g-jj2p says Bun before 1.4.4 is affected and 1.4.4 is the fix. The Hacker News reports the same identifier in Python and in other software. This page does not describe how a stream reaches the bug. Node's versions stay on the Node brief.

The identifier is already on the Node page

This paper's October 21 brief files Node.js 26.12.1, 24.22.1, and 22.23.4, and it names CVE-2026-111497 as the Brotli decoder issue the project rates high. That page's job is those installers. It does not walk the decoder, and this page will not start. The new fact is that the same identifier is not a Node-only patch. NVD's entry describes a buffer overflow in the decoder and names the fixed library versions as 1.0.10, 1.1.1, and 1.2.1. A library version is the upstream fix. A Node version is one product that absorbed it.the Node October release is the installer brief.

Bun's advisory is a different product

Oven's advisory GHSA-663w-cv8g-jj2p says Bun versions before 1.4.4 are affected and that 1.4.4 is the release that updates the bundled Brotli library to the fixed line. The advisory's scope is Bun's own fetch path and its zlib Brotli path, which is who is in scope, not a map of functions. This page does not name parameters, print a request, or describe the malformed stream. The impact the advisory exists to communicate is that a Bun process on the old library can hit the same decoder flaw the Node release was about, and that 1.4.4 is the version Bun says closes it.an advisory is the document that owns the severity.

Python and the proxies stay at the headline

The Hacker News on October 24 says the flaw behind the Node issue also affects Bun, Python, and other widely used software. That headline is why the item is on the wire. Where the article lists proxy builds or configuration changes, this page stops. A list of workarounds is an exploit-adjacent procedure even when a reporter means it as defense. The defensive fact that belongs here is the version: the library lines NVD names, and the Bun release the advisory names. A reader who maintains Envoy or a Python package needs that project's own advisory, not a rewritten table.what a CVE identifier is.

Three documents, three jobs

NVD is the identifier and the library lines. Bun's advisory is one product's fix, with a GHSA number and a version. The Hacker News is the account of spread. Node's blog remains the source for the Node versions, on the other brief. Mixing them into one upgrade instruction would be how a reader patches the wrong runtime. A Bun user is not done because Node shipped. A Node user is not done because Bun shipped. A Python environment is not described by either version number.a patch window is the version you run.

What the overflow sentence is allowed to mean

NVD's description says a crafted stream can overflow a buffer in the decoder. That is the impact: untrusted compressed input, in a product that decodes it, can become a memory-safety bug the vendors rate as serious. It is not an invitation to build the stream. This page has no sample, no offset, and no function trace. The Node brief already refused that trace. Repeating it here would make a second copy of the thing the first brief withheld.

Who is in scope

Operators of Bun before 1.4.4, on Bun's advisory. Operators of the upstream library before the lines NVD names. Operators of Node, who should read the other brief and not this one for their installer. Everyone else who embeds the decoder is in the Hacker News headline and out of a version this page will invent. Omission is not a clean bill. Asked directly, Is this a second writeup of the Node October release? No. That brief already names Node 26.12.1, 24.22.1, and 22.23.4. This page starts where those installers stop, at other products that link the same decoder.

Why this is not the October 21 story

The October 21 story was a release. The October 24 story is the realization, written up by The Hacker News and backed by a Bun advisory, that the release was one consumer of a library bug. Those are different dependencies. The link back is so a reader who started at Node can see the library, and a reader who started here can see the Node versions without this page restating them as if they were new.PHP's later note is a different identifier.

Dates

The Node release is October 21. Bun's advisory and the Python packaging notes clustered on October 23 in the accounts this paper has used. The Hacker News piece is October 24. The library fix versions are whatever NVD lists, not a date. A reader who waits for a single patch Tuesday will miss the product that is not on that Tuesday. Asked directly, Which Bun version does the advisory name? Bun says releases before 1.4.4 are affected and 1.4.4 is the patched release. It says that release updates the Brotli library. This page does not list call sites.

The limit

No trigger. No workaround list. No Node version repeated as the fix for Bun. The record is the identifier, the library lines, and Bun 1.4.4. The short answer this page will stand on is this: NVD describes a buffer overflow in the Brotli decoder and names fixed library lines 1.0.10, 1.1.1, and 1.2.1. Bun's advisory GHSA-663w-cv8g-jj2p says Bun before 1.4.4 is affected and 1.4.4 is the fix. The Hacker News reports the same identifier in Python and in other software. This page does not describe how a stream reaches the bug. Node's versions stay on the Node brief.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. NVD
  2. Bun advisory
  3. The Hacker News

Questions

Is this a second writeup of the Node October release?

No. That brief already names Node 26.12.1, 24.22.1, and 22.23.4. This page starts where those installers stop, at other products that link the same decoder.

Which Bun version does the advisory name?

Bun says releases before 1.4.4 are affected and 1.4.4 is the patched release. It says that release updates the Brotli library. This page does not list call sites.

What does NVD say is fixed?

The library lines it names are 1.0.10, 1.1.1, and 1.2.1. Those are decoder releases, not Node releases and not Bun releases.

Does The Hacker News add a procedure?

It is an account of how widely the decoder is embedded, including Python and proxy software. This page does not reprint workarounds or a byte layout.

Who is in scope if they do not run Node?

Anyone whose product vendors the affected decoder lines. Bun's advisory is the concrete non-Node fix this page will name. A product not on that list is not cleared by omission.