dbcve.org
Traffic ServerApplication · Apache

CVE-2025-31698

HIGH · 7.5 CVSS v3.1 Published 2025-06-19
Fix available
A fix is available. Upgrade to 9.2.11 / 10.0.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Traffic Server ACLs in ip_allow.config or remap.config fail to use the original client IP address provided by PROXY protocol, instead using the proxy's IP. This allows attackers to bypass access control restrictions by connecting through a PROXY protocol-enabled proxy or load balancer.

MitigationUpgrade to version 9.2.11 or 10.0.7 (fixed versions). Alternatively, configure proxy.config.acl.subjects to ensure ACLs evaluate the PROXY protocol-provided IP addresses instead of the proxy's IP.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Traffic ServerApplication
Affected:>= 9.0.0, < 9.2.11>= 10.0.0, < 10.0.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Apache Traffic Server version
    Run 'traffic_server -v' or 'traffic_ctl metric get proxy.node.version.build' to get the version number
    Affected if Version is >= 9.0.0 and < 9.2.11, or >= 10.0.0 and < 10.0.6
  2. Verify PROXY protocol is enabled
    Check the configuration using 'traffic_ctl config get proxy.config.http.insert_forwarded' or inspect records.config for proxy.config.http.insert_forwarded or proxy.config.proxy_protocol.enabled
    Affected if PROXY protocol is enabled (value is set to 1 or a non-zero value)
  3. Inspect ip_allow.config for ACL entries
    Review the ip_allow.config file (typically in /etc/trafficserver/ or /usr/local/etc/trafficserver/) for any ACL rules defined
    Affected if ip_allow.config contains ACL rules that restrict access based on client IP
  4. Inspect remap.config for ACL-based restrictions
    Review remap.config for any @plugin=acl or similar access control configurations that rely on client IP matching
    Affected if remap.config contains ACL rules tied to client IP addresses
  5. Check proxy.config.acl.subjects setting
    Run 'traffic_ctl config get proxy.config.acl.subjects' to see how ACLs are configured to evaluate client addresses
    Affected if proxy.config.acl.subjects is not set to evaluate PROXY protocol-provided IPs (or is unset, defaulting to proxy's own IP)

You are affected if your Apache Traffic Server version falls within the vulnerable range AND PROXY protocol is enabled AND you have ACL rules in ip_allow.config or remap.config that rely on client IP filtering while proxy.config.acl.subjects is not configured to use the PROXY protocol-provided original client IP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.2.11 / 10.0.6 or later
Fixed in 9.2.1110.0.6
Interim mitigation

Upgrade to version 9.2.11 or 10.0.7 (fixed versions). Alternatively, configure proxy.config.acl.subjects to ensure ACLs evaluate the PROXY protocol-provided IP addresses instead of the proxy's IP.

Recommended fix High confidence

9.2.11 or 10.0.6 (depending on your major version branch)

  1. Determine your current Apache Traffic Server version using 'traffic_server -V' or similar command
  2. Plan for a maintenance window as upgrade requires service restart
  3. Backup existing configuration files including ip_allow.config, remap.config, and records.config
  4. For version 9.x: Upgrade to version 9.2.11; For version 10.x: Upgrade to version 10.0.6 using your system's package manager or build from source
  5. Restart Apache Traffic Server to apply the new version
  6. After upgrade, verify the new setting 'proxy.config.acl.subjects' is available in records.config
  7. Test that ACL rules in ip_allow.config and remap.config now correctly use PROXY protocol-provided IP addresses

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31698 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data