WaratekVRT Sign in

CVE-2025-22235

Severity7.3 High CVSS 3.1
Fixed in3.3.11, 3.4.5
WeaknessMissing authorization (CWE-862)
Published28 Apr 2025
Updated17 Jun 2026

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

CWE-20 · Improper input validation

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published a year ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.44% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.springframework.boot:spring-boot 0 none 2.7.24.2
org.springframework.boot:spring-boot 3.1.0 none 3.1.15.2
org.springframework.boot:spring-boot 3.2.0 none 3.2.13.2
org.springframework.boot:spring-boot 3.3.0 3.3.11 unbounded
org.springframework.boot:spring-boot 3.4.0 3.4.5 unbounded

Products and versions

1 product, 5 version entries
SourceVendorProductSchemeAffected versions
osv org.springframework.boot spring-boot generic ≤ 2.7.24.2 · ≥ 3.1.0 and ≤ 3.1.15.2 · ≥ 3.2.0 and ≤ 3.2.13.2 · ≥ 3.3.0 and < 3.3.11 · ≥ 3.4.0 and < 3.4.5

References

URLTags
https://github.com/spring-projects/spring-boot PACKAGE
https://security.netapp.com/advisory/ntap-20250516-0010 WEB
https://spring.io/security/cve-2025-22235 WEB
https://security.netapp.com/advisory/ntap-20250516-0010/

Timeline

Published2025-04-28By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.