dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2026-41854

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.2.18.1 / 7.0.7.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Due to incorrect host parsing, applications that rely on UriComponentsBuilder to parse and validate an externally provided URL string may be exposed to a server-side request forgery (SSRF) attack. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18.

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

UriComponentsBuilder in Spring Framework has incorrect host parsing that allows attackers to bypass validation and inject malicious URLs, leading to SSRF. Applications using UriComponentsBuilder to parse externally provided URL strings without additional validation are vulnerable.

MitigationUpdate to Spring Framework versions 7.0.8+ and 6.2.19+ when available, or implement additional URL validation before using UriComponentsBuilder with untrusted input.

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 FrameworkFramework / library
Affected:>= 6.2.0, < 6.2.18.1>= 7.0.0, < 7.0.7.1

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
None

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

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 Framework version
    Locate the spring-core or spring-framework BOM in your project dependencies (pom.xml, build.gradle, or the JAR manifest). Run 'mvn dependency:tree | grep spring' or 'gradle dependencies | grep spring' to list all Spring dependencies and their resolved versions.
    Affected if The installed version falls within >= 6.2.0 and < 6.2.19, OR >= 7.0.0 and < 7.0.8.
  2. Confirm UriComponentsBuilder usage in codebase
    Search your source code for imports of 'org.springframework.web.util.UriComponentsBuilder' and any method calls such as 'UriComponentsBuilder.fromUriString()', 'UriComponentsBuilder.parseUri()', or similar parsing methods.
    Affected if UriComponentsBuilder is used to construct or parse URLs from any external or untrusted input sources.
  3. Identify data sources feeding UriComponentsBuilder
    Trace back all calls to UriComponentsBuilder methods and identify whether the URL input originates from HTTP request parameters, headers, user-uploaded content, API payloads, or other external sources.
    Affected if External attacker-controlled input (query parameters, path variables, request headers, or body content) is passed to UriComponentsBuilder without prior validation.
  4. Check for SSRF validation layers
    Review your codebase for any existing URL validation logic before UriComponentsBuilder is invoked, such as allowlists of permitted hosts, blocklists of internal IP ranges, or use of libraries likeokhttp or Apache HttpClient with built-in validation.
    Affected if No additional validation exists between the external input source and UriComponentsBuilder, meaning the vulnerability is directly exploitable.

You are affected if your Spring Framework version is between 6.2.0-6.2.18 or 7.0.0-7.0.7 AND external untrusted input is passed directly to UriComponentsBuilder without validation.

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 6.2.18.1 / 7.0.7.1 or later
Fixed in 6.2.18.17.0.7.1
Interim mitigation

Update to Spring Framework versions 7.0.8+ and 6.2.19+ when available, or implement additional URL validation before using UriComponentsBuilder with untrusted input.

Recommended fix High confidence

Spring Framework 6.2.18.1 or 7.0.7.1

  1. 1. Identify all Spring Framework dependencies in your project's build configuration (pom.xml, build.gradle, or similar).
  2. 2. Locate the Spring Framework version declaration - typically in dependencyManagement or directly as spring-core, spring-web, etc.
  3. 3. Update the Spring Framework version to 6.2.18.1 for Spring 6.x users, or to 7.0.7.1 for Spring 7.x users.
  4. 4. In Maven pom.xml, update the version property or dependency like: <spring.version>6.2.18.1</spring.version> or <version.spring>7.0.7.1</version.spring>.
  5. 5. In Gradle, update to: springFrameworkVersion = '6.2.18.1' or '7.0.7.1'.
  6. 6. Rebuild your project to verify the upgrade compiles successfully.
  7. 7. Run your test suite to ensure no regressions from the upgrade.
  8. 8. If using Spring Boot, ensure your Boot version is compatible with the new Framework version.
Caveat Review Spring Framework 6.2 and 7.0 release notes for breaking changes between your current version and the target version

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

Fix this in Spring Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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