# CVE-2025-61581: Apache Traffic Control: ReDoS issue in Traffic Router configuration > Attackers with management access can cause denial of service via malicious regex patterns in Apache Traffic Control, which is now retired. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Oct 2025 - **Updated:** 4 Nov 2025 - **Also known as:** GHSA-9m49-p2j3-c6xm, GO-2025-4033 ## What is CVE-2025-61581? CVE-2025-61581 is a high-severity denial of service vulnerability in Apache Traffic Control, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ** 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. Weakness: CWE-1333 (Inefficient Regular Expression Complexity) ## Which versions are affected by CVE-2025-61581? 4 open source packages ship an affected version, including github.com/apache/trafficcontrol/v8 and github.com/apache/trafficcontrol. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/apache/trafficcontrol/v8` | Go | All versions | None | | `github.com/apache/trafficcontrol/v8` | Go | All versions to 8.0.2 | None | | `github.com/apache/trafficcontrol/v8` | Go | All versions to 8.0.2 | None | | `github.com/apache/trafficcontrol` | Go | All versions | None | Products: Apache Traffic Control. ## How do I fix CVE-2025-61581? Product is end of life, replace it. ## Is CVE-2025-61581 being exploited? There is no known exploitation of CVE-2025-61581 in the wild and no public exploit code. ## Other vulnerabilities in Apache Traffic Control - [CVE-2024-45387](https://insights.sbomify.com/CVE-2024-45387/): Apache Traffic Control: SQL Injection in Traffic Ops endpoint PUT deliveryservice_request_comments (critical 9.9) - [CVE-2021-43350](https://insights.sbomify.com/CVE-2021-43350/): LDAP filter injection vulnerability in Traffic Ops (critical 9.8) - [CVE-2019-12405](https://insights.sbomify.com/CVE-2019-12405/): Improper Authentication in Apache Traffic Control (critical 9.8) - [CVE-2022-23206](https://insights.sbomify.com/CVE-2022-23206/): Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth (high 7.5) - [CVE-2017-7670](https://insights.sbomify.com/CVE-2017-7670/): Apache Traffic Control vulnerable to Slowloris-style Denial of Service attack (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-61581 and fix it if it is affected. What it is: CVE-2025-61581 is a high-severity denial of service vulnerability in Apache Traffic Control, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-61581 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/apache/trafficcontrol/v8 (Go): affected all versions; no fix listed - github.com/apache/trafficcontrol/v8 (Go): affected all versions up to 8.0.2; no fix listed - github.com/apache/trafficcontrol/v8 (Go): affected all versions up to 8.0.2; no fix listed - github.com/apache/trafficcontrol (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-61581/ (Markdown: https://insights.sbomify.com/CVE-2025-61581/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61581 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61581 - OSV: https://osv.dev/vulnerability/CVE-2025-61581 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-61581/ Summaries are generated and may contain mistakes; the official description above is the record.