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

New CVE Detected

CVE-2026-58178 – Denial of Service (Uncontrolled Recursion in ESI Plugin) – Apache Traffic Server 8.

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

Summary

CVE-2026-58178 is an uncontrolled recursion vulnerability (CWE-674) in the Edge Side Includes (ESI) plugin of Apache Traffic Server. A remote, unauthenticated attacker can leverage the plugin to recursively fetch attacker-controlled URLs without bounds, exhausting server resources and resulting in a denial-of-service condition. The issue carries a CVSS v3.1 base score of 7.5 (HIGH).

Technical details

  • Root cause: The ESI plugin fails to enforce bounds on recursion when processing Edge Side Includes directives, allowing nested/recursive fetches to grow without limit (CWE-674: Uncontrolled Recursion).
  • Trigger conditions: Requires that the ESI plugin is enabled and that ESI processing can be induced to fetch attacker-controlled URLs, which are then recursively resolved.
  • Attack vector: Network (AV:N). The vulnerability is remotely reachable and requires no authentication or user interaction.
  • Impact: High availability impact. Uncontrolled recursion exhausts server resources, causing a denial of service for the affected Traffic Server instance. There is no confirmed impact to confidentiality or integrity.

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

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4 (or later), which contain the fix. Note that no fixed release is listed for the 8.x branch; users running 8.0.0–8.1.9 should migrate to a supported, patched release line.
  • If no patch can be applied immediately: Disable the ESI plugin if it is not required, or restrict/validate the URLs the ESI plugin is permitted to fetch so attacker-controlled recursive fetches cannot be triggered. Apply upstream network controls to limit exposure of the affected service until patching is complete.

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