Apache Traffic Server: heap-buffer-overflow

Apache Traffic Server

Apache Traffic Server has a heap-buffer-overflow vulnerability via HTTP Host header

Do this now

Check the Apache Traffic Server advisory for a fix and restrict untrusted clients meanwhile.

First seen: 3 Nov 2026
Last update: 3 Nov 2026, 20:19 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Apache Traffic Server: heap-buffer-overflow
Severity: unknown. Patch status: fix status unknown.
Affected: Apache Traffic Server

Apache Traffic Server has a heap-buffer-overflow vulnerability via HTTP Host header

## Steps
1. Search the repo, its CI and infra config for Apache Traffic Server. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://seclists.org/oss-sec/2026/q4/480
https://pwned.coffee/i/apache-traffic-server-heap-buffer-overflow

Timeline

3 Nov 2026, 20:19 UTC
Fix status: no fix yet → unknown.
3 Nov 2026
First reported.

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 4 Nov 2026, 08:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

seclists.org: Apache Traffic Server: heap-buffer-overflow via HTTP Host header (unbounded alloca pattern, 5 sites) — 90-day disclosure

Totalone coffee