dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-22235

HIGH · 7.3 CVSS v3.1 Published 2025-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

When EndpointRequest.to() references a disabled or non-web-exposed actuator endpoint, it incorrectly creates a security matcher for 'null/**' instead of handling the disabled state properly. This can cause requests to /null paths to be mishandled in Spring Security chain configurations, potentially exposing endpoints that should be protected.

MitigationEnsure all actuator endpoints referenced by EndpointRequest.to() in Spring Security configurations are enabled and web-exposed, or remove EndpointRequest.to() calls for disabled endpoints and explicitly secure any /null paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Security configuration using EndpointRequest.to()
    Search codebase for 'EndpointRequest.to(' patterns in SecurityFilterChain or WebSecurityConfigurerAdapter classes
    Affected if EndpointRequest.to() is used in security configuration to reference actuator endpoints
  2. List all actuator endpoints referenced by EndpointRequest.to()
    Extract all endpoint IDs passed to EndpointRequest.to() calls in security configuration (e.g., EndpointRequest.to("health", "info"))
    Affected if Any disabled or non-web-exposed actuator endpoint is referenced
  3. Verify referenced actuator endpoints are enabled
    Check application.properties/application.yml for 'management.endpoint.<endpoint-id>.enabled=true' for each endpoint referenced by EndpointRequest.to()
    Affected if Any endpoint referenced by EndpointRequest.to() has enabled set to false or is not explicitly enabled
  4. Verify referenced actuator endpoints are web-exposed
    Check application.properties/application.yml for 'management.endpoints.web.exposure.include' to confirm referenced endpoints are included in the exposed list
    Affected if Any endpoint referenced by EndpointRequest.to() is not included in web.exposure.include
  5. Inspect security chain for null path matchers
    Review SecurityFilterChain configuration for any 'null/**' or similar wildcard matchers that may have been inadvertently created
    Affected if Security configuration contains matcher for 'null/**' or requests to /null are unexpectedly permitted
  6. Test actual endpoint accessibility
    Send HTTP requests to /null path and verify they are not accessible when they should be protected
    Affected if Requests to /null paths are allowed through the security chain when they should be blocked

A user is affected if their Spring Security configuration uses EndpointRequest.to() to reference any actuator endpoint that is disabled or not web-exposed, resulting in unintended security matcher behavior for null paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure all actuator endpoints referenced by EndpointRequest.to() in Spring Security configurations are enabled and web-exposed, or remove EndpointRequest.to() calls for disabled endpoints and explicitly secure any /null paths.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data