Spring FrameworkFramework / library · VMware
CVE-2026-41844
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 · uneditedA Spring MVC or Spring WebFlux application which configures a mapping for "/**" where the view name is not explicitly specified allows an attacker to craft a link resulting in a 302 redirect to an arbitrary external host via the redirect: prefix. 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 confidenceOpen redirect vulnerability in Spring MVC/WebFlux applications where a catch-all mapping for '/**' without an explicit view name allows attackers to craft malicious links using the 'redirect:' prefix, resulting in 302 redirects to arbitrary external domains.
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
>= 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.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Spring Framework versionCheck your project's dependency manifest (Maven pom.xml, Gradle build.gradle, or the spring-core JAR manifest) to determine the exact Spring Framework version in useAffected if The version falls within any of these ranges: 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
-
Verify wildcard URL mapping configurationInspect your Spring MVC controller mappings and view controller configurations. Look for any @RequestMapping, @GetMapping, or view controller definitions using the /** wildcard pattern, particularly in your WebMvcConfigurer or annotation-based controller classesAffected if Any controller or view controller is mapped to /** (the catch-all wildcard)
-
Check for implicit view name usageReview your controller methods that return String types without explicit view names, or check if any view resolver configurations rely on implicit view name resolution based on request URLsAffected if Controllers return view names implicitly derived from request URLs (e.g., method returning "home" based on request to /home)
-
Inspect ViewResolver configurationExamine your Spring MVC configuration for InternalResourceViewResolver, ThymeleafViewResolver, or other view resolver beans. Check for prefix/suffix settings and any chain configurations that might enable redirect: prefix handlingAffected if A view resolver is configured and the application processes view names that could accept the redirect: prefix for external redirects
You are affected if your Spring Framework version is vulnerable AND you have wildcard (/**) mappings combined with implicit view name resolution that could process a redirect: prefix in the URL.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.3.496.1.286.2.18.1
Update to patched Spring Framework versions (7.0.8+, 6.2.19+, 6.1.28+, 5.3.49+) or avoid using '/**' mappings without explicit view names and implement URL validation for redirect targets.
Spring Framework 5.3.49, 6.1.28, 6.2.18.1, or 7.0.7.1 (choose based on your major version branch)
- 1. Identify the current Spring Framework version in use (check pom.xml, build.gradle, or dependencies)
- 2. Determine the appropriate upgrade path based on your current major version (5.3.x -> 5.3.49, 6.1.x -> 6.1.28, 6.2.x -> 6.2.18.1, 7.0.x -> 7.0.7.1)
- 3. Update the Spring Framework version in your build configuration file to the fixed version
- 4. Rebuild the application with the updated dependencies
- 5. Run existing tests to verify no regressions were introduced
- 6. Deploy the updated application
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
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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