Skip to main content
VulnerabilityPublished Updated

CVE-2025-31698: Apache Traffic Server · Improper Access Control

Affects Apache Traffic ServerSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 10.0.6 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.0.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Apache Traffic Server to 10.0.6.

Affected software

ProductAffectedFixed in
Apache Software Foundation Apache Traffic ServerAffected
  • =10.0.0
  • =9.0.0
  • =9.0.0 <=9.2.10
  • >=10.0.0 <10.0.6
Fixed in
  • 10.0.6

AI-suggested

Beyond upgrading to Apache Traffic Server versions 9.2.11 or 10.0.6 or later, organizations should: 1) Audit current ACL configurations in ip_allow.config and remap.config to ensure they correctly reflect intended access policies, especially in environments using the PROXY protocol. 2) Explicitly configure the proxy.config.acl.subjects setting to define which IP addresses are considered for ACL decisions, avoiding reliance on default or ambiguous settings. 3) Implement network segmentation and additional layers of access control to reduce reliance on ACLs alone for security. 4) Monitor logs for unusual access patterns or unexpected IP addresses that may indicate attempts to exploit this vulnerability. 5) Conduct penetration testing focusing on ACL bypass scenarios in proxy-enabled environments. 6) Review and update incident response plans to include scenarios involving ACL bypass and unauthorized access through proxy protocols. These steps will help ensure that even if the vulnerability is present, the risk of exploitation is minimized.

Description

ACL configured in ip_allow.config or remap.config does not use IP addresses that are provided by PROXY protocol. Users can use a new setting (proxy.config.acl.subjects) to choose which IP addresses to use for the ACL if Apache Traffic Server is configured to accept PROXY protocol. This issue affects undefined: from 10.0.0 through 10.0.6, from 9.0.0 through 9.2.10. Users are recommended to upgrade to version 9.2.11 or 10.0.6, which fixes the issue.

References

Community reviews

Loading reviews…