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

New CVE Detected

CVE-2026-58157 – Cross-Connection Information Disclosure – Apache Traffic Server 8.0.0–8.1.9, 9.0.0–

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

Summary

CVE-2026-58157 is an information-disclosure vulnerability in Apache Traffic Server caused by improper reuse of server sessions and tunnels, which can expose data across separate client connections. An unauthenticated, network-based attacker may be able to obtain sensitive information belonging to other clients. The issue is rated HIGH severity with a CVSS v3.1 base score of 8.7.

Technical details

  • Root cause: Apache Traffic Server can improperly reuse server sessions and tunnels, allowing state associated with one client connection to be exposed on another (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor).
  • Trigger conditions: Occurs when the proxy reuses upstream/server sessions and tunnels across distinct client connections rather than keeping them isolated.
  • Attack vector: Network (remote); no authentication or user interaction required. High attack complexity.
  • Impact: Sensitive data can leak between separate client connections, resulting in high confidentiality and integrity impact and a scope change (data crossing a trust boundary between clients).

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

Mitigation and recommended actions

  • Immediate: Upgrade to a fixed release:
    • 9.x branch: upgrade to 9.2.15 or later
    • 10.x branch: upgrade to 10.1.4 or later
  • If no patch can be applied immediately: The 8.x branch is affected and out of the actively fixed release lines, so migrate to a supported, patched release (9.2.15+ or 10.1.4+). Because the flaw stems from improper server session/tunnel reuse, review and restrict connection-reuse and keep-alive settings between the proxy and origin servers where feasible until upgrading, and monitor for anomalous cross-client data exposure.

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