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

Back
New CVE Detected

CVE-2026-58159 – IP Access Control Bypass – Apache Traffic Server 8.0.0–10.1.3

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58159 is a high-severity incorrect authorization vulnerability (CWE-863) in Apache Traffic Server (ATS) that allows unauthenticated remote attackers to bypass IP-based access controls. The flaw exists in two distinct areas: IP access control enforcement on Unix Domain Socket (UDS) listeners, and errors in ACL matching logic. It carries a CVSS v3.1 base score of 8.2 (HIGH) and affects ATS versions 8.0.0 through 10.1.3 across all three supported branches.

Technical details

  • Root cause: Incorrect authorization logic (CWE-863) affecting two separate mechanisms — IP access control on UDS listeners is not properly enforced, and ACL matching contains errors that allow unintended traffic to pass.
  • Trigger conditions: An attacker sends network requests to an Apache Traffic Server instance; no credentials, special configuration, or user interaction are required.
  • Attack vector: Fully remote and unauthenticated (AV:N/AC:L/PR:N/UI:N); the attack can be carried out over the internet against any exposed ATS instance.
  • Impact: Successful exploitation allows an attacker to bypass IP allowlist controls that are intended to restrict access to trusted sources, reaching endpoints or backend services that should otherwise be blocked. CVSS rates Integrity impact as HIGH and Availability impact as LOW; Confidentiality impact is rated NONE.

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

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which contain the vendor-provided fix. No patch has been issued for the 8.x branch; organizations running 8.x should migrate to a supported and patched release.
  • If immediate patching is not possible: Apply strict network-level controls (firewall rules, network segmentation) to limit which hosts can reach ATS listeners. Review and audit all IP-based ACL configurations on UDS listeners and TCP listeners to verify they are enforcing restrictions as intended.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge