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

Back
New CVE Detected

CVE-2026-58159 – IP Access Control (ACL) Authorization Bypass – Apache Traffic Server 8.0.0–8.1.9, 9

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58159 is an incorrect-authorization (CWE-863) vulnerability in Apache Traffic Server that allows remote attackers to bypass IP-based access controls. The flaw stems from faulty ACL matching logic and incorrect handling of IP access controls on Unix Domain Socket (UDS) listeners, enabling requests that should be denied to reach protected resources. It carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: Incorrect authorization logic (CWE-863) in Apache Traffic Server’s ACL matching, combined with improper enforcement of IP access controls on Unix Domain Socket (UDS) listeners.
  • Trigger conditions: An attacker sends requests through Traffic Server whose evaluation against the configured IP access-control rules is mishandled, causing rules that should block the request to be bypassed.
  • Attack vector: Network (AV:N), low attack complexity, no privileges and no user interaction required.
  • Impact: Circumvention of configured access-control restrictions, resulting in high impact to integrity and a low impact to availability; attackers may reach resources or functionality intended to be restricted.

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 a fixed release — Apache Traffic Server 9.2.15 or later, or 10.1.4 or later.
  • If no patch can be applied immediately: Review and tighten IP access-control configurations (e.g., ip_allow.config and remap.config ACL rules), restrict or disable exposure of UDS listeners where feasible, and use upstream network controls (firewalls/segmentation) to limit which clients can reach Traffic Server listeners until the upgrade is completed.

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