Case · DiggingBeagle record

Node.js credits Codex Security for a Brotli memory-safety finding

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
not established
Evidence
Grade B
Remediation
patch available
AI role
WITH AI
Basis and provenance

CLM-NODE-BROTLI-111497-1 reports: CVE-2026-111497 affects Node.js 26.x, 24.x and 22.x. The October 21 release set lists versions 26.12.1, 24.22.1 and 22.23.4. Source SRC-2026-CP17-NODE-OCT21 is located at 'Node.js Brotli decoder out-of-bounds write; Downloads and release details'. The distinctive mechanism begins: The Node.js October security notice identifies an out-of-bounds write in Brotli decompression with potential remote code execution, and credits OpenAI Codex Security researchers Khai Tran and Sylvie Mayer alongside the named fix authors. Classification: setting=research_demonstration, exploit_status=not_established, evidence_grade=B on the bounded original investigator/vendor or paper evidence, without independent dynamic replication. remediation_status=patch_available; scoped control or limit: Upgrade affected Node.js major versions to the October 21 fixed releases; treat advisory severity as a warning of possible impact, not evidence that a remote exploit was observed. The null impact band avoids an ungrounded cross-Case severity rating; observed damage, targeted population and controlled test outcomes cannot be exchanged as the same quantity. Where a patch is described, its availability is separate from independently tested effectiveness.

Assessed Oct 23, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 21, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-NODE-BROTLI-111497-1CVE-2026-111497 affects Node.js 26.x, 24.x and 22.x. The October 21 release set lists versions 26.12.1, 24.22.1 and 22.23.4.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Upgrade affected Node.js major versions to the October 21 fixed releases; treat advisory severity as a warning of possible impact, not evidence that a remote exploit was observed.

Unknowns and contradictions

  • No exploit was executed here; production exploitation and the exact human/model division are unspecified.

Sources and citation

Material revision history

  1. Oct 23, 2026 · Canonical change recorded · new in release · revision 183