CVE-2025-49763 | Apache Traffic Server: Remote DoS via memory exhaustion in ESI Plugin

ESI plugin does not have the limit for maximum inclusion depth, and that allows excessive memory consumption if malicious instructions are inserted. Users can use a new setting for the plugin (--max-inclusion-depth) to limit it. This issue affects Apache Traffic Server: from 10.0.0 through 10.0.5, 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: 2025-07-01 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-49763 is rated Moderate Risk (42.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.63%). Mandatory action: 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-49763

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 4.01% 0.63% -3.38%
2 2026-06-07 3.37% 4.01% +0.64%
3 2026-04-17 3.37%

Full EPSS history (24 records total)

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

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:N/I:N/A:H 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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-49763

OS Trackers for CVE-2025-49763

vendor priority summary link
debian not yet assigned CVE-2025-49763 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-49763
redhat high https://access.redhat.com/security/cve/CVE-2025-49763
ubuntu medium CVE-2025-49763 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-49763

Affected software / configurations for CVE-2025-49763

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-49763

cvelogic Threat Intelligence