CVE-2025-29313 — odl-sfc-openflow-renderer
HIGHCVE-2025-29313 is a high-severity (CVSS 7.5) CWE-404 vulnerability in org.opendaylight.sfc:odl-sfc-openflow-renderer. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
OpenDaylight SFC Denial of Service (DoS)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-29313.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.opendaylight.sfc:odl-sfc-openflow-renderer☕org.opendaylight.sfc:odl-sfc-ovsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Use of incorrectly resolved name or reference in OpenDaylight Service Function Chaining (SFC) Subproject SFC Sodium-SR4 and below allows attackers to cause a Denial of Service (DoS).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opendaylight.sfc:odl-sfc-openflow-renderer | all versions | No fix |
| ☕Maven | org.opendaylight.sfc:odl-sfc-ovs | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opendaylight.sfc:odl-sfc-openflow-renderer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.opendaylight.sfc:odl-sfc-openflow-renderer for CVE-2025-29313. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2025-29313 in your dependencies?
Find it across Maven, including transitive dependencies.