dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2026-41843

MEDIUM · 5.9 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 →
68/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 Path Traversal attacks when resolving static resources. 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 · moderate confidence

Spring Framework contains a path traversal vulnerability in static resource resolution for MVC and WebFlux applications. The vulnerability allows attackers to use '..' sequences to potentially access files outside the intended static resource directory.

MitigationUpgrade to Spring Framework 7.0.8+, 6.2.19+, 6.1.28+, or 5.3.49+ respectively, or implement input validation to reject paths containing traversal sequences.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 the Spring Framework version in your application
    Check your build configuration (pom.xml for Maven, build.gradle for Gradle) for the spring-core or spring-webmvc/spring-webflux dependency version, or run your build tool's dependency tree command to list the Spring Framework version.
    Affected if The installed version is 5.3.0 through 5.3.48, 6.1.0 through 6.1.27, 6.2.0 through 6.2.18, or 7.0.0 through 7.0.7.
  2. Determine if static resource serving is enabled
    Inspect your Spring MVC or WebFlux configuration (either XML configuration files or @Configuration classes with @EnableWebMvc or @EnableWebFlux annotations) for ResourceHandlerRegistry or ResourceHandlerMapping definitions.
    Affected if Resource handlers are configured to serve static content from the classpath, file system, or web root directories.
  3. Verify resource location configuration
    Review your resource handler registration code for the addResourceLocations() method calls. Check what paths are configured as static resource sources (e.g., classpath:/static/, file:/var/resources/, /WEB-INF/resources/).
    Affected if Resource locations allow access to directories outside the intended web root, or use overly permissive path patterns.
  4. Inspect web application deployment structure
    Examine your WAR or JAR deployment to identify the web root directory and confirm which directories are intended to serve static content versus those that should remain protected.
    Affected if Static resource handlers are mapped to the root path (/) or broad path patterns that could allow traversal outside the intended static content directory.

You are affected if your Spring Framework version falls within the affected ranges AND your application configures static resource handlers that could serve files from paths accessible via directory traversal sequences.

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 to Spring Framework 7.0.8+, 6.2.19+, 6.1.28+, or 5.3.49+ respectively, or implement input validation to reject paths containing traversal sequences.

Recommended fix High confidence

Upgrade to Spring Framework 5.3.49+, 6.1.28+, 6.2.18.1+, or 7.0.7.1+ (choose the appropriate branch)

  1. 1. Identify the current Spring Framework version in your project (check pom.xml, build.gradle, or dependency management)
  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.49 or later
  4. 4. For Spring Framework 6.1.x: upgrade to version 6.1.28 or later
  5. 5. For Spring Framework 6.2.x: upgrade to version 6.2.18.1 or later
  6. 6. For Spring Framework 7.0.x: upgrade to version 7.0.7.1 or later
  7. 7. Update the Spring Framework dependency in your build configuration file
  8. 8. Rebuild and test the application to verify the upgrade does not break existing functionality
Caveat Spring Framework patch releases typically maintain backward compatibility; standard regression testing recommended

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-41843 — 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-41843 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