Quick answers
- Is CVE-2026-112381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112381 being exploited in the wild.
- How severe is CVE-2026-112381?
- Medium severity, with a CVSS score of 5.9, published 21 October 2026.
- Which products and versions are affected?
- Apache Traffic Server 9.2.15, 10.1.4, 10.2.0.
- Is there a fix for CVE-2026-112381?
- Yes: fixed in 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-112381 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-112381?
- 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: 9.2.16, 10.1.5, 10.2.1
Technical details
A null pointer dereference occurs in a reentrant write-ready callback when a client half-closes a POST request while a chunked origin response is being reparsed. This race condition was introduced by flow-control backports for CVE-2021-32564. The crash is timing-dependent and requires specific conditions: a POST request tear-down via half-close concurrent with origin response reparse from a write-ready callback. A remote attacker can exploit this over the network to cause a denial of service.
Affected products
- Apache Traffic Server 9.2.15, 10.1.4, 10.2.0
Timeline
- 2026-10-21: disclosed