cve.bz

CVE-2025-22235 spring spring boot: Improper Input Validation

7.3 highEPSS 0.4%Fix available

High (7.3) in spring spring boot. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.boot:spring-boot 3.3.11, 3.4.5.

On this page
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

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-04-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • org.springframework.boot:spring-boot (Maven): fixed in 3.3.11, 3.4.5

Ask an AI about this CVE

Show the promptExplain CVE-2025-22235 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-22235?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-22235?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-22235 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Bootfrom 2.7.x before 2.7.25
Spring Bootfrom 3.1.x before 3.1.16
Spring Bootfrom 3.2.x before 3.2.14
Spring Bootfrom 3.3.x before 3.3.11
Spring Bootfrom 3.4.x before 3.4.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rc42-6c7j-7h5rMavenorg.springframework.boot:spring-boot<=2.7.24.2no fix published
GHSA-rc42-6c7j-7h5rMavenorg.springframework.boot:spring-boot>=3.1.0 <=3.1.15.2no fix published
GHSA-rc42-6c7j-7h5rMavenorg.springframework.boot:spring-boot>=3.2.0 <=3.2.13.2no fix published
GHSA-rc42-6c7j-7h5rMavenorg.springframework.boot:spring-boot>=3.3.0 <3.3.113.3.11
GHSA-rc42-6c7j-7h5rMavenorg.springframework.boot:spring-boot>=3.4.0 <3.4.53.4.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu25.10, 26.04:LTS, 26.10 and 6 morelibspring-javano fix listedUBUNTU-CVE-2025-22235

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

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

Red Hat's mitigation

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.

ProductPackageStateAdvisory
A-MQ Clients 2spring-bootAffected
Red Hat AMQ Broker 7spring-bootNot affected
Red Hat AMQ Clientsspring-bootAffected
Red Hat build of Apache Camel for Spring Boot 4spring-bootNot affected
Red Hat build of OptaPlanner 8spring-bootWill not fix
Red Hat Data Grid 8spring-bootWill not fix
Red Hat Enterprise Linux 8log4j:2/log4jNot affected
Red Hat Enterprise Linux 9log4jNot affected
Red Hat Fuse 7spring-bootWill not fix
Red Hat Integration Camel K 1spring-bootWill not fix
Red Hat JBoss Enterprise Application Platform 7spring-bootWill not fix
Red Hat JBoss Enterprise Application Platform 8spring-bootNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packspring-bootNot affected
Red Hat Process Automation 7spring-bootNot affected
Red Hat Single Sign-On 7spring-bootNot affected
streams for Apache Kafkaspring-bootWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-22235.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON