Spring FrameworkFramework / library · VMware
CVE-2026-41849
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 · uneditedAn integer overflow vulnerability exists in the evaluation logic of the Spring Expression Language (SpEL). An attacker can exploit this by supplying a specially crafted SpEL expression that triggers excessive resource consumption, resulting in a Denial of Service (DoS). Affected versions: Spring Framework 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 confidenceAn integer overflow vulnerability exists in the Spring Expression Language (SpEL) evaluation logic within Spring Framework 5.3.0-5.3.48. Attackers can exploit this by supplying specially crafted SpEL expressions that trigger the overflow, leading to excessive resource consumption and denial of service.
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.49CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Framework dependencyInspect your project's build configuration (pom.xml for Maven, build.gradle for Gradle) or the application's classpath to locate spring-core or spring-expression JAR files and note their version.Affected if Spring Framework is present in the application
-
Determine Spring Framework versionCheck the exact version of spring-core or spring-expression JAR in your deployed application. For Maven projects, run 'mvn dependency:tree' or 'mvn dependency:list'. For Gradle, run 'gradle dependencies'. For deployed WAR/JAR files, inspect the META-INF/MANIFEST.MF or check the filename of the Spring JAR directly.Affected if The version is 5.3.0 through 5.3.48 (inclusive)
-
Verify SpEL is in useSearch your codebase for imports of 'org.springframework.expression' packages, usage of SpelExpressionParser, or Spring bean configurations that define expression-based properties (using 'spel' or expression language in property values).Affected if SpEL parsing or evaluation is actively used in the application
-
Check if SpEL evaluates external inputReview code paths where SpEL expressions are evaluated and trace whether any user-supplied data (HTTP request parameters, headers, file content, database values, API inputs) can influence the expression string passed to SpEL parser.Affected if User-controlled or externally-sourced data can reach SpEL expression evaluation without validation
Your environment is affected if you use Spring Framework versions 5.3.0 through 5.3.48 and your application evaluates SpEL expressions that can be influenced by external input.
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.49
Upgrade Spring Framework to version 5.3.49 or later to patch the integer overflow vulnerability in SpEL processing.
Spring Framework 5.3.49
- Identify all applications and services that depend on Spring Framework versions 5.3.0 through 5.3.48
- Update the Spring Framework dependency in your project's pom.xml or build.gradle file to version 5.3.49 or later
- Run dependency resolution to ensure the correct version is pulled (e.g., mvn dependency:tree or ./gradlew dependencies)
- Rebuild the application and run your test suite to verify functionality
- Deploy the updated application to your environments
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Framework
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41849 — 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-41849 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