CVE-2025-22235 — spring-boot
HIGHCVE-2025-22235 is a high-severity (CVSS 7.3) Improper Input Validation vulnerability in org.springframework.boot:spring-boot. A fix is available for org.springframework.boot:spring-boot — see the affected versions and patch details below.
Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-22235.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-22235 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.springframework.boot:spring-boot☕org.springframework.boot:spring-boot☕org.springframework.boot:spring-boot☕org.springframework.boot:spring-boot☕org.springframework.boot:spring-bootReal-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
EndpointRequest.to() creates a matcher for null/** if the actuator endpoint, for which the EndpointRequest has been created, is disabled or not exposed.
Your application may be affected by this if all the following conditions are met:
- You use Spring Security
- EndpointRequest.to() has been used in a Spring Security chain configuration
- The endpoint which EndpointRequest references is disabled or not exposed via web
- Your application handles requests to /null and this path needs protection
You are not affected if any of the following is true:
- You don't use Spring Security
- You don't use EndpointRequest.to()
- The endpoint which EndpointRequest.to() refers to is enabled and is exposed
- Your application does not handle requests to /null or this path does not need protection
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.boot:spring-boot | all versions | No fix |
| ☕Maven | org.springframework.boot:spring-boot | ≥ 3.1.0 | No fix |
| ☕Maven | org.springframework.boot:spring-boot | ≥ 3.2.0 | No fix |
| ☕Maven | org.springframework.boot:spring-boot | ≥ 3.3.0&&< 3.3.11 | 3.3.11org.springframework.boot:spring-boot:3.3.11 |
| ☕Maven | org.springframework.boot:spring-boot | ≥ 3.4.0&&< 3.4.5 | 3.4.5org.springframework.boot:spring-boot:3.4.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.springframework.boot:spring-boot has shipped for CVE-2025-22235 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-22235 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-22235. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-22235 in your dependencies?
O3 Security finds CVE-2025-22235 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.