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

New CVE Detected

CVE-2026-58179 – Stack-Based Buffer Overflow (Remote Memory Corruption) – Apache Traffic Server 8.0.

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

Summary

CVE-2026-58179 is a stack-based buffer overflow (with associated integer overflow) in the regex_remap plugin of Apache Traffic Server. When the plugin builds a substitution string from crafted input, it overflows the stack and mishandles integer arithmetic on the substitution input, leading to memory corruption. The issue is rated HIGH severity (CVSS v3.1 base score 8.1) and is remotely reachable over the network.

Technical details

  • Root cause: The regex_remap plugin overflows the stack and mishandles integers when expanding substitution input during regular-expression remap rewriting (CWE-121: Stack-based Buffer Overflow, combined with an integer-overflow condition).
  • Trigger conditions: An affected server must be configured to use the regex_remap plugin. The overflow is reached when the plugin processes attacker-influenced substitution input through its regex replacement functionality.
  • Attack vector: Network (AV:N). The condition is triggered through requests handled by the proxy’s remap processing; the vector carries high attack complexity (AC:H) and requires no privileges or user interaction.
  • Impact: Memory corruption with high impact to confidentiality, integrity, and availability of the Traffic Server process.

Affected software

Apache Traffic Server (Apache Software Foundation):

  • 8.0.0 through 8.1.9
  • 9.0.0 through 9.2.14
  • 10.0.0 through 10.1.3

Severity

  • CVSS v3.1: Base score 8.1 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate (patch): Upgrade to Apache Traffic Server 9.2.15 or 10.1.4 (or later), which fix this issue.
  • If patching is not immediately possible: Where operationally feasible, avoid using the regex_remap plugin and remove regex_remap substitution rules that process untrusted input until the upgrade can be applied. Restrict network exposure of affected Traffic Server instances to trusted sources.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge