Whether a target endpoint is exposed to CVE-2026-111497, the out-of-bounds write in Google Brotli 1.0.3–1.2.0, as reached through the software that decodes incoming Brotli streams.
It sends four one-byte control requests to learn how the endpoint handles valid Brotli JSON, malformed Brotli, requests without a JSON content type, and unsupported encodings. It then streams a 23,068,764-byte Brotli probe and repeats the valid control. A target is reported vulnerable only when the full probe reaches the valid route-response class, the malformed-response class is distinct, and the final control confirms the endpoint remained stable. The scanner does not execute a command on the target, but it is active testing, not a passive version read.
It is an active test and should be treated as such. Each tested endpoint receives five one-byte requests and one 23,068,764-byte Brotli probe. The probe is sent with Expect: 100-continue, so a proxy can reject its advertised size before the body is uploaded. The URL path you submit is preserved (defaulting to /), and redirects are not followed. Run it only against endpoints you own or are authorized to test.
Vulnerable — the full-size probe reached the same response class as the valid control, while the malformed-request control produced a distinct response and the endpoint stayed stable afterward.
No Signal — the probe's response didn't match the vulnerable pattern; no evidence of the flaw was found on this endpoint.
Inconclusive — the scanner couldn't complete one of its control requests, so no verdict could be reached.
No. Only submit endpoints you own or have explicit written authorization to test. Sending active test traffic to systems you don't control may be unlawful.
Yes. We only collect the target URL and email address to perform the scan and deliver results. Scan data and submitted email address are not shared, sold, or used for marketing. Information is retained only for operational and security purposes and handled in accordance with industry-standard data protection practices.
Update any Brotli library in the 1.0.3–1.2.0 range to a fixed release (1.0.10, 1.1.1, or 1.2.1), and update the runtimes that bundle it — Node.js to 22.23.4 / 24.22.1 / 26.12.1, Bun to 1.4.4, and the Python Brotli / brotlicffi packages to 1.2.1 / 1.2.1.0. Node.js 20 and earlier are end-of-life and won't be patched, so move those to a supported version. Then restart every process, rebuild and redeploy your containers, and update lockfiles so the vulnerable version isn't pulled back in.
Yes. If your application is vulnerable or you want further assurance, we can assist with remediation guidance, patch validation, and in-depth penetration testing. Our team can also perform broader assessments covering web applications, APIs, infrastructure, and AI deployments to ensure the vulnerability is fully addressed and no additional risks remain.