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

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.

Published: 2025-06-19 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31698 is rated Moderate Risk (42.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-31698

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.75% 0.45% -0.31%
2 2026-04-17 0.74% 0.75% +0.01%
3 2026-04-15 — 0.74% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-31698

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-31698

OS Trackers for CVE-2025-31698

vendor priority summary link
debian not yet assigned CVE-2025-31698 not yet assigned priority: Debian including 1 source packages (trafficserver), 3 status rows across 3 suites (bookworm, bullseye, sid): open 2, resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-31698
redhat medium — https://access.redhat.com/security/cve/CVE-2025-31698
ubuntu medium CVE-2025-31698 medium priority: Ubuntu including 1 source packages (trafficserver), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needed 3, needs-triage 3, ignored 2, released 1. https://ubuntu.com/security/CVE-2025-31698

Affected software / configurations for CVE-2025-31698

Vendor Product Version Raw CPE
apache traffic_server >= 9.0.0, < 9.2.11 cpe:2.3:a:apache:traffic_server:*:*:*:*:*:*:*:*
apache traffic_server >= 10.0.0, < 10.0.6 cpe:2.3:a:apache:traffic_server:*:*:*:*:*:*:*:*

References for CVE-2025-31698

cvelogic Threat Intelligence