Quick answers
- Is CVE-2026-111812 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111812 being exploited in the wild.
- How severe is CVE-2026-111812?
- Critical severity, with a CVSS score of 10, published 21 October 2026.
- Which products and versions are affected?
- Apache Traffic Server 8.0.0–8.1.11, 9.0.0–9.2.15, 10.0.0–10.1.4, 10.2.0.
- Is there a fix for CVE-2026-111812?
- Yes: fixed in Traffic Server 9.2.16, 10.1.5, 10.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111812 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-111812?
- Check whether you run Apache Traffic Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Traffic Server 9.2.16, 10.1.5, 10.2.1
Technical details
A credential signing bypass exists in Apache Traffic Server's origin_server_auth plugin where an unauthenticated client can force the plugin to sign attacker-controlled AWS request headers using the proxy's own credentials. The vulnerability is triggered by crafting malicious HTTP requests that manipulate the header signing logic. An attacker with network access can exploit this remotely to forge valid AWS signatures and make unauthorized API calls.
Affected products
- Apache Traffic Server 8.0.0–8.1.11, 9.0.0–9.2.15, 10.0.0–10.1.4, 10.2.0
Timeline
- 2026-10-21: disclosed