CVE-2025-61581 | Apache Traffic Control: ReDoS issue in Traffic Router configuration

** UNSUPPORTED WHEN ASSIGNED ** Inefficient Regular Expression Complexity vulnerability in Apache Traffic Control. This issue affects Apache Traffic Control: all versions. People with access to the management interface of the Traffic Router component could specify malicious patterns and cause unavailability. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Published: 2025-10-16 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61581 is rated Moderate Risk (49.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.32%). 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-61581

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-03-26 0.17% 0.32% +0.15%
2 2026-03-14 0.26% 0.17% -0.09%
3 2026-02-15 — 0.26% —

Full EPSS history (8 records total)

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

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

GitHub Security Advisory for CVE-2025-61581

GHSA-9m49-p2j3-c6xm · Severity: low · Ecosystem: go — Apache Traffic Control has an Inefficient Regular Expression Complexity vulnerability

Affected software / configurations for CVE-2025-61581

Vendor Product Version Raw CPE
apache traffic_control <= 8.0.2 cpe:2.3:a:apache:traffic_control:*:*:*:*:*:*:*:*

References for CVE-2025-61581

cvelogic Threat Intelligence