dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2026-22740

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-29
Fix available
A fix is available. Upgrade to 5.3.48 / 6.1.27 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space. Older, unsupported versions are also affected.

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 WebFlux server applications create temp files for multipart request parts larger than 10KB. Due to a bug in the file cleanup mechanism, these temp files may not be deleted after request processing completes, allowing an attacker to exhaust disk space by sending repeated large multipart requests.

MitigationUpgrade to a patched version of Spring WebFlux that properly cleans up multipart temp files after request completion, or implement automated cleanup of the temp directory.

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.48>= 6.1.0, < 6.1.27>= 6.2.0, < 6.2.18>= 7.0.0, < 7.0.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify Spring Framework version
    Check your project's dependency management (pom.xml, build.gradle, or the spring-core/spring-webflux JAR manifest) to find the exact Spring Framework version in use
    Affected if The version falls outside the safe ranges: 5.3.48+, 6.1.27+, 6.2.18+, or 7.0.7+
  2. Confirm Spring WebFlux is in use
    Verify that spring-webflux (or spring-boot-starter-webflux) is included as a dependency in your application
    Affected if Spring WebFlux is present as a dependency and the Spring Framework version is vulnerable as identified above
  3. Check if multipart handling is enabled
    Review your WebFlux configuration or application properties for multipart file upload settings (such as spring.webflux.multipart.* or @EnableWebFlux with MultipartResolver beans)
    Affected if Multipart request handling is enabled and the application processes file uploads via WebFlux
  4. Inspect temp directory for lingering files
    Monitor the system's default temp directory (java.io.tmpdir) or the configured Spring WebFlux temp directory for orphaned multipart temp files that persist after requests complete
    Affected if Undeleted temp files accumulate in the temp directory, especially files larger than 10KB from multipart requests that are not cleaned up after processing

Your environment is affected if you run a vulnerable Spring Framework version (below 5.3.48, 6.1.27, 6.2.18, or 7.0.7) with Spring WebFlux enabled and multipart file upload handling configured.

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.48 / 6.1.27 / 6.2.18 or later
Fixed in 5.3.486.1.276.2.18
Interim mitigation

Upgrade to a patched version of Spring WebFlux that properly cleans up multipart temp files after request completion, or implement automated cleanup of the temp directory.

Recommended fix High confidence

Spring Framework 5.3.48 (for 5.3.x branch), 6.1.27 (for 6.1.x branch), 6.2.18 (for 6.2.x branch), or 7.0.7 (for 7.0.x branch)

  1. 1. Identify the current Spring Framework version in your project (check pom.xml or build.gradle for spring-core or spring-webflux version)
  2. 2. Determine which version branch you are on: 5.3.x, 6.1.x, 6.2.x, or 7.0.x
  3. 3. For Spring Framework 5.3.x: upgrade to version 5.3.48
  4. 4. For Spring Framework 6.1.x: upgrade to version 6.1.27
  5. 5. For Spring Framework 6.2.x: upgrade to version 6.2.18
  6. 6. For Spring Framework 7.0.x: upgrade to version 7.0.7
  7. 7. Update the version in your dependency management (pom.xml or build.gradle)
  8. 8. Rebuild the project and run tests to verify compatibility
Caveat Patch releases typically have minimal breaking changes; review the Spring Framework release notes for any migration notes

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

Fix this in Spring Framework Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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