dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2026-41853

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 5.3.49 / 6.1.28 or later.
See remediation →
62/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
Spring MVC and WebFlux applications are vulnerable to Multipart request smuggling attacks. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.

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

Spring MVC and WebFlux applications are vulnerable to multipart request smuggling attacks, where attackers can manipulate HTTP multipart requests to bypass security controls or cause the server to misinterpret request boundaries.

MitigationUpgrade Spring Framework to version 7.0.8+, 6.2.19+, 6.1.28+, or 5.3.49+ to obtain the patched versions.

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:>= 5.3.0, < 5.3.49>= 6.1.0, < 6.1.28>= 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installed Spring Framework version
    Locate the spring-core or spring-framework-bom version in your project dependencies (pom.xml, build.gradle, or Maven/Gradle lock files). If running as a dependency, run: mvn dependency:tree | grep spring-core or check the classpath at runtime.
    Affected if The version is 5.3.0 to 5.3.48, 6.1.0 to 6.1.27, 6.2.0 to 6.2.18, or 7.0.0 to 7.0.7.
  2. Confirm multipart support is enabled
    Check your application configuration files (application.properties or application.yml) for the property spring.servlet.multipart.enabled=true, or look for a MultipartResolver bean definition in your Java configuration.
    Affected if Multipart support is enabled (spring.servlet.multipart.enabled=true or a MultipartResolver bean exists).
  3. Identify multipart request handling endpoints
    Search your codebase for @PostMapping, @RequestMapping, or other handler methods that accept MultipartFile parameters, or examine your routes/configuration for file upload endpoints.
    Affected if The application processes multipart requests (file uploads, forms with file attachments).

You are affected if your Spring Framework version falls within the vulnerable ranges AND your application has multipart request handling enabled and actively processes multipart uploads.

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 5.3.49 / 6.1.28 / 6.2.18.1 or later
Fixed in 5.3.496.1.286.2.18.1
Interim mitigation

Upgrade Spring Framework to version 7.0.8+, 6.2.19+, 6.1.28+, or 5.3.49+ to obtain the patched versions.

Recommended fix High confidence

Spring Framework 5.3.49, 6.1.28, 6.2.18.1, or 7.0.7.1 (depending on your current major version branch)

  1. Identify the current Spring Framework version in your project (check pom.xml, build.gradle, or dependency management)
  2. Determine which major version branch you are on (5.3.x, 6.1.x, 6.2.x, or 7.0.x)
  3. For Spring Framework 5.3.x: upgrade to version 5.3.49
  4. For Spring Framework 6.1.x: upgrade to version 6.1.28
  5. For Spring Framework 6.2.x: upgrade to version 6.2.18.1
  6. For Spring Framework 7.0.x: upgrade to version 7.0.7.1
  7. Update the dependency version in your build configuration file
  8. Run build and tests to verify compatibility
Caveat Review Spring Framework release notes for any breaking changes between your current version and the target fixed version; minor version upgrades typically have minimal breaking changes

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

Fix this in Spring Framework Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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