An update to my earlier post on HTTP2Shell, the critical Brotli decoder bug that also hit Node.js (linked below). Cisco has been refreshing its product advisory for that issue and a handful of related October Node.js flaws, and the latest revision, 1.13, is dated November 13.
The underlying bugs are the ones I already wrote about, including CVE-2026-111497 in Google’s Brotli decoder, plus DNS and TLS-hostname issues in Node.js. What’s new is the Cisco-shaped question: which of their products actually bundle the vulnerable code, and what do you apply. Cisco says that if a product is not listed, its review indicates it is not affected. Several core networking and firewall lines are called out as not impacted, including Catalyst SD-WAN, ISE, IOS XE, IOS XR, ASA, FMC and FTD. NX-OS shows up in the detailed tables, mainly around Guest Shell on some Nexus 3000 and 9000 switches, with fixed Guest Shell or NX-OS releases listed on a staggered schedule. Other products already have, or are getting, fixed releases, including some Duo, Packet Tracer, Intersight and collaboration components. A further set is still under investigation, and some fix dates are still marked TBD.
I’m not going to walk through the bug mechanics. If you run Cisco gear, or Cisco software that might ship Node.js or Brotli, read the current advisory for your product and apply the fixed software when Cisco has one. Don’t assume a general Node.js upgrade on the side covers a bundled copy.
Review before you install: read the release notes yourself, back up your config, and try new versions somewhere you can afford to break first.
My take
This is the long tail of a library bug: the first week is “patch Node,” and the next month is “who else shipped a copy.” Check the list, patch what you have, and don’t ignore a TBD if that product sits on a network you care about. Cisco is still updating the advisory, so look at the dated revision, not a screenshot from October.
God Bless, and Happy hacking!