Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.46% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-41842High confidence
Spring Framework Denial of Service via Versioned Resources in Spring MVC and WebFlux
Spring · Spring Framework
7.5HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Spring Spring Framework and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | libspring-java | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian bookwormbookworm · source | libspring-java | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian forkyforky · source | libspring-java | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian sidsid · source | libspring-java | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | libspring-java | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Open-source package ranges16 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.springframework:spring-webflux | ECOSYSTEM: introduced 7.0.0; fixed 7.0.8 | 7.0.8 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webflux | ECOSYSTEM: introduced 6.2.0; fixed 6.2.19 | 6.2.19 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webflux | ECOSYSTEM: introduced 6.1.0; last affected 6.1.21 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webflux | ECOSYSTEM: introduced 0; last affected 5.3.39 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webmvc | ECOSYSTEM: introduced 7.0.0; fixed 7.0.8 | 7.0.8 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webmvc | ECOSYSTEM: introduced 6.2.0; fixed 6.2.19 | 6.2.19 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webmvc | ECOSYSTEM: introduced 6.1.0; last affected 6.1.21 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework:spring-webmvc | ECOSYSTEM: introduced 0; last affected 5.3.39 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.springframework:spring-webflux | >= 7.0.0, <= 7.0.7 | 7.0.8 | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webflux | >= 6.2.0, <= 6.2.18 | 6.2.19 | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webflux | >= 6.1.0, <= 6.1.21 | Not stated | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webflux | <= 5.3.39 | Not stated | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webmvc | >= 7.0.0, <= 7.0.7 | 7.0.8 | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webmvc | >= 6.2.0, <= 6.2.18 | 6.2.19 | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webmvc | >= 6.1.0, <= 6.1.21 | Not stated | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
| mavenorg.springframework:spring-webmvc | <= 5.3.39 | Not stated | GitHub advisory ↗github reviewed aggregator · 30 Jul 2026 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) 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.
What
Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) 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.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) 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.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Uncontrolled Resource Consumption → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Security Bulletin - August 18 2026 | Atlassian Support | Atlassian Documentation →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026Unable to load Security Bulletin - August 18 2026 Security Advisories & Bulletins November 2022: Atlassian Security Advisories Overview Archived Security Advisories Security Advisories for Apps July 2022: Atlassian Security Advisories Overview August 2022: Atlassian Security Advisories Overview January 2023: Secur
04
Evidence and provenance
Published 9 Jun 2026 · Last source change 27 Jun 2026, 20:59 UTC · CWE-400 · Uncontrolled Resource Consumption
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-35330
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.