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

New CVE Detected

CVE-2026-58177 – Out-of-Bounds Write / Path Traversal / Use-After-Free – Apache Traffic Server 10.0.

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

Summary

CVE-2026-58177 is a set of memory-safety and path-traversal flaws in the Cripts scripting framework of Apache Traffic Server. The issues include out-of-bounds writes (CWE-787), path traversal, and use-after-free errors affecting Apache Traffic Server versions 10.0.0 through 10.1.3. It carries a CVSS v3.1 base score of 8.1 (HIGH).

Technical details

  • Root cause: Multiple memory-safety and input-handling defects in the Cripts framework — the C++ scripting/plugin layer used to author remap and global processing logic in Apache Traffic Server. The defects include out-of-bounds writes (CWE-787), path traversal, and use-after-free conditions.
  • Trigger conditions: Exploitation requires specific conditions to be met (reflected in the High attack complexity of the CVSS vector), such as the server running affected Cripts-based logic that mishandles attacker-influenced input.
  • Attack vector: Network (AV:N). The vulnerability is reachable remotely without authentication (PR:N) and without user interaction (UI:N).
  • Impact: Successful exploitation can lead to out-of-bounds memory writes and use-after-free conditions, and path traversal beyond intended file boundaries. The CVSS scope is Changed (S:C), with low confidentiality and integrity impact and high availability impact — consistent with memory corruption that can crash or destabilize the service and expose or alter limited data.

Affected software

  • Apache Traffic Server 10.0.0 through 10.1.3 (inclusive).

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 10.1.4 or later, which resolves these issues.
  • If no patch can be applied immediately: Review and restrict any Cripts-based remap/global logic that processes untrusted input, and place network access controls in front of the proxy to limit exposure of the management and request-handling surface until the upgrade can be completed.

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