Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112381 Overview
CVE-2026-112381 is a null pointer dereference vulnerability in Apache Traffic Server (ATS). The flaw occurs when a client POST request is torn down via half-close while a chunked origin response is being reparsed from a reentrant write-ready callback. This timing-dependent race was introduced by the flow-control backports made for CVE-2021-32564. A remote attacker can trigger the condition over the network without authentication, causing the proxy process to crash and producing a denial-of-service condition.
Critical Impact
Unauthenticated remote attackers can crash Apache Traffic Server instances by triggering a race between client half-close and chunked response reparsing, disrupting proxy availability for all downstream clients.
Affected Products
- Apache Traffic Server 9.2.15
- Apache Traffic Server 10.1.4
- Apache Traffic Server 10.2.0
Discovery Timeline
- 2026-10-21 - CVE-2026-112381 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-112381
Vulnerability Analysis
The defect is a classic null pointer dereference [CWE-476] triggered by a race condition in Apache Traffic Server's HTTP state machine. When a client issues a POST request and then performs a TCP half-close while the origin server is still delivering a chunked transfer-encoded response, ATS enters a reentrant code path. A write-ready callback reparses the chunked response body while the associated session state is being torn down. The teardown nullifies internal structures that the reparse routine still references, and dereferencing those pointers crashes the server process.
Because the flaw is triggered by ordinary HTTP behavior, exploitation requires no credentials and no user interaction. The impact is limited to availability: the Traffic Server process aborts, interrupting all in-flight connections.
Root Cause
The race was introduced by backports of flow-control fixes made for CVE-2021-32564. Those backports altered the ordering of state transitions in the write-ready callback path. The reparser now runs reentrantly against session state that the half-close handler may concurrently invalidate, leaving a window in which a pointer is read after it has been cleared.
Attack Vector
An attacker initiates a POST request through the proxy to an origin that responds with Transfer-Encoding: chunked. The attacker then performs a TCP half-close on the client socket while the origin response is still streaming. If the write-ready callback fires during the teardown, ATS dereferences a null pointer and the process crashes. Full technical discussion is available in the Apache Mailing List Thread.
No verified public exploit code is available at this time. The vulnerability mechanism is described in prose only.
Detection Methods for CVE-2026-112381
Indicators of Compromise
- Unexpected traffic_server process crashes, segmentation faults, or core dumps on proxy hosts running affected versions.
- Repeated client connections that issue POST requests followed immediately by shutdown(SHUT_WR) against origins returning chunked responses.
- Gaps or restarts in ATS access logs correlating with elevated 5xx responses to downstream clients.
Detection Strategies
- Monitor traffic.out, diags.log, and system journal entries for null pointer dereference stack traces referencing the chunked response parser or write-ready callback.
- Correlate process restart events with network flow records showing abnormal POST-and-half-close sequences from the same client IP addresses.
- Deploy network IDS signatures that flag high rates of POST requests terminated by client FIN before the response body completes.
Monitoring Recommendations
- Alert on traffic_server process restarts and watchdog-initiated respawns.
- Track origin responses using Transfer-Encoding: chunked paired with abrupt client disconnects as a behavioral baseline.
- Forward ATS crash telemetry and reverse-proxy logs to a centralized SIEM for correlation with upstream traffic patterns.
How to Mitigate CVE-2026-112381
Immediate Actions Required
- Upgrade Apache Traffic Server to version 9.2.16, 10.1.5, or 10.2.1 as applicable to your deployed branch.
- Inventory all ATS instances and confirm running versions using traffic_server --version across the fleet.
- Enable automatic process supervision (for example, systemd restart policies) to limit downtime while patches are being deployed.
Patch Information
The Apache Traffic Server project has released fixed versions 9.2.16, 10.1.5, and 10.2.1. These releases correct the ordering of state transitions between the half-close handler and the chunked response reparser invoked by the write-ready callback. Refer to the Apache Mailing List Thread for release details and upgrade guidance.
Workarounds
- No official configuration-only workaround is published. Upgrading to a fixed release is the recommended remediation.
- As a temporary risk reduction, place a stable upstream load balancer in front of ATS to absorb client half-close patterns and distribute load across multiple proxy processes.
- Restrict proxy exposure to trusted client ranges where feasible until patched versions are deployed.
# Verify installed Apache Traffic Server version
traffic_server --version
# Example upgrade path on Debian/Ubuntu once patched packages are available
sudo apt-get update
sudo apt-get install --only-upgrade trafficserver
sudo systemctl restart trafficserver
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

