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

Back
New CVE Detected

CVE-2026-58179 – Stack-Based Buffer Overflow / Potential RCE – 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-58179 is a high-severity stack-based buffer overflow vulnerability (CWE-121) in the regex_remap plugin of Apache Traffic Server (ATS), caused by insufficient bounds checking on substitution input. The flaw also triggers integer overflows during the same processing path. With a CVSS v3.1 score of 8.1 (High) and full Confidentiality, Integrity, and Availability impact scores (C:H/I:H/A:H), the vulnerability carries significant risk of complete system compromise on affected servers where the plugin is active.

Technical details

  • Root cause: The regex_remap plugin performs URL rewriting by applying user-supplied regex patterns and substitution strings (e.g., $0–$9, $h, $p, $q). When processing substitution input, the plugin fails to enforce proper bounds, leading to both a stack-based buffer overflow and integer overflows.
  • Trigger conditions: The vulnerability is reachable over the network without authentication or user interaction; however, it requires that the regex_remap plugin be loaded and active in the ATS configuration, and that attacker-controllable input reaches the substitution processing logic (AC:H).
  • Attack vector: Network-accessible; no privileges or user interaction required (AV:N/PR:N/UI:N).
  • Impact: CVSS impact metrics of C:H/I:H/A:H indicate potential for full system compromise across confidentiality, integrity, and availability — consistent with the severity of a stack-based buffer overflow in a network-facing plugin.

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: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0: 9.2 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Apache Traffic Server to version 9.2.15 or 10.1.4, which contain the official fix from the Apache Software Foundation. Note that the 8.x branch does not have a patched release; organizations running 8.x should migrate to a supported branch (9.2.15 or 10.1.4).
  • If immediate patching is not possible: Disable or remove the regex_remap plugin from the ATS configuration to eliminate the vulnerable code path. Restrict network access to ATS instances to trusted clients where feasible.

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