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
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.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
A fix is available for CVE-2025-22235; check the affected-versions list above or the advisory for the patched release of org.springframework.boot:spring-boot, then make sure no transitive dependency still pins the vulnerable range.
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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
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…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-22235 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-22235 in your dependencies?
Find it across Maven, including transitive dependencies.