Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-58154 – Out-of-Bounds Write / Integer Overflow – Apache Traffic Server 8.0.0–10.1.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58154 is a high-severity memory corruption vulnerability (CWE-787: Out-of-Bounds Write) in Apache Traffic Server (ATS), the open-source reverse proxy and HTTP caching server published by the Apache Software Foundation. The flaw is triggered during MIME and HTTP header parsing, where ATS can write out of bounds or overflow integers when processing crafted header input. With a CVSS v3.1 score of 8.9 (HIGH), the vulnerability requires no authentication and no user interaction, and carries a changed scope — meaning it can affect resources beyond the vulnerable component itself.

Technical details

  • Root cause: Out-of-bounds write and integer overflow conditions in the MIME and HTTP header parsing routines of Apache Traffic Server (CWE-787: Out-of-Bounds Write).
  • Trigger conditions: An attacker sends a specially crafted HTTP request containing malicious MIME or HTTP headers to any ATS instance reachable over the network. No authentication is required and no user interaction is needed.
  • Attack vector: Network (AV:N) — ATS operates as a reverse proxy at the network edge and processes all inbound HTTP traffic, making the vulnerable parsing code path directly reachable from the internet.
  • Impact: The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H) indicates Scope Changed, High Integrity Impact, and High Availability Impact — consistent with potential memory state corruption, proxy destabilization, or disruption of downstream systems served by the proxy.
  • No public proof-of-concept exploit has been identified at the time of publication.

Affected software

  • Apache Traffic Server 8.0.0 through 8.1.9
  • Apache Traffic Server 9.0.0 through 9.2.14
  • Apache Traffic Server 10.0.0 through 10.1.3

Severity

CVSS v3.1 Base Score: 8.9 (HIGH)
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H

Mitigation and recommended actions

  • Immediate – Patch: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which contain the official fix issued by the Apache Software Foundation. Note that the 8.x branch has no patch available; organizations running any 8.x version should migrate to a supported and patched branch (9.2.15 or 10.1.4).
  • If immediate patching is not feasible: Restrict network-level access to ATS listening interfaces using firewall rules or upstream ACLs to limit exposure to trusted sources only, and monitor HTTP traffic for anomalous or malformed header payloads.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge