Skip to content
Fencer Vulns
high 7.3

CVE-2025-22235 json

Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed

published 2025-04-28 18 mo ago modified 2026-09-10 1 mo ago also GHSA-rc42-6c7j-7h5r , EUVD-2025-12575

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.springframework.boot:spring-boot 3.3.11, 3.4.5
  • Spring Spring Boot 2.7.25, 3.1.16, 3.2.14, 3.3.11, 3.4.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-22235 updated cvss 7.3

org.springframework.boot/spring-boot: Spring Boot EndpointRequest.to() creates wrong matcher if actuator endpoint is not exposed

  • Red Hat A-MQ Clients 2 spring-boot Red Hat AMQ Clients spring-boot
    affected: workaround, no fix available
  • Red Hat build of OptaPlanner 8 spring-boot Red Hat Data Grid 8 spring-boot Red Hat Fuse 7 spring-boot Red Hat Integration Camel K 1 spring-boot Red Hat JBoss Enterprise Application Platform 7 spring-boot Red Hat streams for Apache Kafka spring-boot
    affected: workaround, no fix planned “Will not fix”
  • Red Hat AMQ Broker 7 spring-boot
    not affected: component not present
  • Red Hat build of Apache Camel for Spring Boot 4 spring-boot
    not affected: inline mitigations already exist
  • Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j Red Hat JBoss Enterprise Application Platform 8 spring-boot Red Hat JBoss Enterprise Application Platform Expansion Pack spring-boot
    not affected: vulnerable code not present
  • Red Hat Process Automation 7 spring-boot Red Hat Single Sign-On 7 spring-boot
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
GitHub 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.springframework.boot:spring-boot
<=2.7.24.2
>=3.1.0, <=3.1.15.2
>=3.2.0, <=3.2.13.2
>=3.3.0, <3.3.11
>=3.4.0, <3.4.5
3.3.11
3.4.5

Affected products

  • Spring Spring Boot

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.