AI Science Tracker

HTTP/2 compressed headers can amplify server memory usage with built-in TLS

Yopass · AI involvement attributed to Anthropic's OSS Scanner

Finding and attribution

Yopass leaves MaxHeaderBytes unset on its application and metrics listeners. An unauthenticated client can repeat HPACK-compressed cookie fields across concurrent HTTP/2 requests; Go expands the headers into per-request strings retained while bodies are pending. Requires an HTTP/2-enabled built-in TLS listener or a proxy that forwards large decoded headers. Historical releases without HTTP/2 support are not exposed to this variant; this does not reveal secret content or bypass secret authorization.

Product: Yopass. AI system: Anthropic's OSS Scanner. Team / organization: Anthropic.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The Yopass maintainer's case-specific security advisory explicitly credits Anthropic's OSS Scanner as discoverer (tracking identifier ANT-2026-AX5EL1AH). It does not name a model version or internal discovery date.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The public maintainer advisory documents the finding; it does not establish whether defenders knew of it or whether it was exploited before disclosure.

Remediation status: fix documented. Yopass 16.0.0 fixes the issue (commit 23b56941c7597690e17907f90d4c0fe6d90049a). Affected-version scope: Built-in TLS versions 4.0.1 through 15.1.0, subject to runtime and listener configuration; fixed in 16.0.0 by setting MaxHeaderBytes to 16 KiB on both listeners. Patch availability does not establish downstream deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 17 Oct 2026. AI attribution dated 17 Oct 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: denial of service.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: denial of service.
Prerequisites / affected scope: Repeated concurrent requests can degrade availability or exhaust process/container memory under the stated HTTP/2 and listener conditions..
Exploitation evidence: The advisory describes a possible or reproducible trigger as stated; it does not report observed exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: Yopass 16.0.0 fixes the issue (commit 23b56941c7597690e17907f90d4c0fe6d90049a). Affected-version scope: Built-in TLS versions 4.0.1 through 15.1.0, subject to runtime and listener configuration; fixed in 16.0.0 by setting MaxHeaderBytes to 16 KiB on both listeners. Patch availability does not establish downstream deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases