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

New CVE Detected

CVE-2026-58163 – Cache State Corruption / Integrity Impact – Apache Traffic Server 8.0.0–10.1.3

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

Summary

CVE-2026-58163 is a high-severity vulnerability in Apache Traffic Server (ATS), an open-source reverse proxy and caching server widely deployed at the internet edge. The flaw stems from deserialization of untrusted data (CWE-502): ATS mishandles on-disk cache fields and object lifetimes, leading to cache state corruption or server crashes. It is exploitable remotely without authentication and carries a CVSS v3.1 score of 7.5 (HIGH).

Technical details

  • Root cause: Improper deserialization of on-disk cache fields and mismanagement of object lifetimes (CWE-502), allowing the cache subsystem to reach a corrupt state when processing attacker-influenced cached content.
  • Trigger conditions: The vulnerability can be triggered remotely over the network with no privileges and no user interaction required (CVSS PR:N, UI:N, AC:L).
  • Attack vector: Network-reachable (AV:N); ATS exposes itself via standard HTTP response headers (Server: ATS/x.x.x, Via, X-Cache), making instances trivially identifiable and targetable.
  • Impact: High integrity impact (I:H) — corrupted cache state can cause ATS to serve manipulated or malicious content to downstream users. The official description also explicitly identifies crashes as an outcome, indicating real availability impact beyond what the CVSS v3.1 vector alone captures. The CVSS v4.0 score (8.3 HIGH) reflects Availability: High at the base level.

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 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CVSS v4.0 Base Score: 8.3 HIGH — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which contain the official fix released by the Apache Software Foundation.
  • Users on the 8.x branch should migrate to a supported release line (9.2.15 or 10.1.4), as no patch has been issued for the 8.x series.
  • If immediate patching is not possible, restrict public network access to ATS instances and suppress version-disclosing response headers to limit fingerprinting.

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

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