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

Back
New CVE Detected

CVE-2026-58188 – Out-of-Bounds Write / DoS and Limit Bypass in Experimental Plugins – Apache Traf…

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58188 is a high-severity vulnerability affecting Apache Traffic Server (ATS), a widely deployed enterprise-grade reverse proxy, caching, and load-balancing server. The flaw involves out-of-bounds write errors (CWE-787) and limit-bypass issues in several experimental ATS plugins, exposing affected deployments to denial-of-service conditions and potential security control circumvention. With a CVSS v3.1 score of 8.2 (HIGH), no authentication required, and no user interaction needed, internet-facing ATS deployments running experimental plugins should be patched immediately.

Technical details

  • Root cause: Out-of-bounds write (CWE-787) and limit-bypass errors residing in multiple experimental Apache Traffic Server plugins.
  • Trigger conditions: The vulnerability is present only in deployments where experimental ATS plugins have been explicitly enabled. No authentication or user interaction is required to trigger the flaw once a vulnerable plugin is active.
  • Attack vector: Remotely exploitable over the network (AV:N) with low attack complexity (AC:L) and no privileges required (PR:N).
  • Impact: High availability impact — out-of-bounds write conditions can crash or destabilize ATS proxy nodes, causing service disruption across critical internet-facing infrastructure. A secondary integrity impact (I:L) indicates that limit-bypass conditions may permit circumvention of request controls or rate-limiting enforcement. No confidentiality impact is indicated by the CVSS scoring.

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.2 (HIGH)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which contain the official fix. No patched release has been issued for the 8.x branch; administrators running versions 8.0.0–8.1.9 should migrate to a supported and patched 9.x or 10.x release.
  • If immediate patching is not feasible: Disable all experimental plugins to eliminate the vulnerable attack surface. Additionally, apply network-level access controls to restrict inbound traffic to ATS instances where operationally possible.

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