dbcve.org
Spring BootFramework / library · VMware

CVE-2026-22733

HIGH · 8.1 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 2.7.32 / 3.3.18 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requires authentication is declared under the path used by the CloudFoundry Actuator endpoints. This issue affects Spring Security: from 4.0.0 through 4.0.3, from 3.5.0 through 3.5.11, from 3.4.0 through 3.4.14, from 3.3.0 through 3.3.17, from 2.7.0 through 2.7.31.

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 · moderate confidence

Authentication bypass vulnerability in Spring Security where endpoints requiring authentication can be accessed without credentials when declared under the path used by CloudFoundry Actuator endpoints. The actuator endpoint path configuration overrides or bypasses standard Spring Security authentication checks.

MitigationUpgrade Spring Security to a patched version beyond 4.0.3/3.5.11/3.4.14/3.3.17/2.7.31, and audit endpoint path configurations to ensure protected endpoints do not share paths with CloudFoundry Actuator endpoints.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring BootFramework / library
Affected:< 2.7.32>= 3.3.0, < 3.3.18>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.12>= 4.0.0, < 4.0.4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Spring Boot version
    Inspect your project's build configuration file (pom.xml or build.gradle) for the Spring Boot version, or examine the spring-boot-*.jar file in your deployment.
    Affected if The installed version falls within < 2.7.32; >= 3.3.0, < 3.3.18; >= 3.4.0, < 3.4.15; >= 3.5.0, < 3.5.12; or >= 4.0.0, < 4.0.4.
  2. Verify CloudFoundry Actuator endpoints are enabled
    Check your application.properties or application.yml for management.endpoints.web.exposure.include configuration, or for any programmatic actuator endpoint registration.
    Affected if Actuator endpoints are exposed (such as /health, /info, /env, or similar).
  3. Identify actuator base path configuration
    Examine application.properties (management.endpoints.web.base-path) or application.yml for the configured actuator base path, typically defaulting to '/actuator'.
    Affected if A custom actuator base path is configured that could overlap with protected endpoints.
  4. Review endpoint path mappings
    Inspect your controller and security configurations to map all registered endpoints and their required authentication settings. Compare these against the actuator path.
    Affected if Any protected endpoints share a path prefix with the configured actuator endpoint path (such as '/actuator' or a custom path).

You are affected if your Spring Boot version is within the affected ranges AND CloudFoundry Actuator endpoints are enabled AND your protected endpoints share paths with the actuator endpoint path configuration.

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.

dbcve · scoped
Upgrade available Upgrade to 2.7.32 / 3.3.18 / 3.4.15 or later
Fixed in 2.7.323.3.183.4.15
Interim mitigation

Upgrade Spring Security to a patched version beyond 4.0.3/3.5.11/3.4.14/3.3.17/2.7.31, and audit endpoint path configurations to ensure protected endpoints do not share paths with CloudFoundry Actuator endpoints.

Recommended fix High confidence

Spring Boot 2.7.32 (or 3.3.18, 3.4.15, or 3.5.12 depending on your branch)

  1. 1. Identify your current Spring Boot version from your pom.xml or build.gradle file
  2. 2. Determine the next appropriate fixed version based on your current branch: if using 2.7.x, upgrade to 2.7.32 or later; if using 3.3.x, upgrade to 3.3.18 or later; if using 3.4.x, upgrade to 3.4.15 or later; if using 3.5.x, upgrade to 3.5.12 or later
  3. 3. Update the Spring Boot version in your build configuration (pom.xml: <spring-boot.version> or build.gradle: springBoot { version })
  4. 4. Run your build to verify all dependencies resolve correctly
  5. 5. Run your test suite to ensure existing functionality is not broken
  6. 6. If using custom security configurations, verify that actuator endpoints under /cloudfoundryapplication path are properly secured
  7. 7. Deploy to a staging environment and verify authentication is working correctly on all endpoints
Caveat Major version upgrades (2.x to 3.x) may require Java 17+, changes to Jakarta EE namespaces, and potential breaking changes in Spring Security configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Boot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22733 — 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-2026-22733 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