Spring FrameworkFramework / library · VMware
CVE-2026-41850
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 · uneditedApplications that evaluate user-supplied Spring Expression Language (SpEL) expressions are vulnerable to an Algorithmic Denial of Service (DoS). By providing a specially crafted expression, an attacker can trigger excessive resource consumption during evaluation, leading to application degradation or unavailability. 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 confidenceApplications that evaluate user-supplied Spring Expression Language (SpEL) expressions are vulnerable to an Algorithmic Denial of Service (DoS) attack. Specially crafted SpEL expressions can trigger excessive resource consumption during evaluation, causing application degradation or unavailability.
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
- 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 versionLocate the spring-core or spring-context JAR file in your application's classpath and check its version metadata. Common locations: WEB-INF/lib directory, Maven dependencies (mvn dependency:tree), or Gradle dependencies (gradle dependencies). The version is typically visible in the JAR filename or dependency report.Affected if The installed version falls within 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.
-
Determine if SpEL is used in the applicationSearch code for imports of org.springframework.expression and usage of SpelExpressionParser or ExpressionParser. Also check for @Value annotations with expressions, SpelExpressionParser instances, or any code paths that parse expressions from strings.Affected if The application uses SpelExpressionParser or any SpEL parsing mechanism to evaluate expressions.
-
Check if user input reaches SpEL evaluationAudit code paths where SpEL expressions are evaluated. Look for patterns where request parameters, headers, query strings, or any external input flows into SpelExpressionParser.parseExpression() or similar evaluation methods. Trace data flow from HTTP endpoints to SpEL evaluation points.Affected if User-supplied or external data (HTTP parameters, headers, file contents, database values) can be passed as the expression string to be evaluated.
-
Inspect SpEL configuration and expression beansReview Spring configuration files (XML, Java config, or properties) for beans of type Expression or SpelExpressionParser. Check for any custom evaluators or expression templates that may accept runtime values. Look for template-based expression usage like ExpressionTemplate.Affected if Expression beans are configured to accept dynamic or external expression strings at runtime.
You are affected if your application runs a vulnerable Spring Framework version AND evaluates user-supplied SpEL expressions from external input sources.
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
Upgrade Spring Framework to version 5.3.49, 6.1.28, 6.2.19, or 7.0.8 or later. Additionally, avoid evaluating user-supplied SpEL expressions; if unavoidable, implement expression sandboxing, evaluation timeouts, and input length/validation constraints.
Spring Framework 5.3.49+ / 6.1.28+ / 6.2.18.1+ / 7.0.7.1+ (choose the appropriate version line for your current major.minor)
- 1. Identify all applications and dependencies that use Spring Framework and evaluate SpEL expressions from user input.
- 2. For Spring Framework 5.3.x: Upgrade to version 5.3.49 or later.
- 3. For Spring Framework 6.1.x: Upgrade to version 6.1.28 or later.
- 4. For Spring Framework 6.2.x: Upgrade to version 6.2.18.1 or later.
- 5. For Spring Framework 7.0.x: Upgrade to version 7.0.7.1 or later.
- 6. Rebuild and redeploy all affected applications with the updated Spring Framework dependencies.
- 7. Test applications to verify they function correctly with the new Spring Framework version.
- 8. If immediate upgrade is not possible, implement input validation to reject or sanitize user-supplied SpEL expressions before evaluation, and configure expression evaluation timeouts if supported.
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
- Implementation2.0 h
- Testing6.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,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41850 — 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-41850 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