LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47892: Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints

A WebFlux application using functional endpoints and deployed with DispatcherServlet may be vulnerable to a header predicate bypass in a pre-flight request. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.5.RELEASE - 5.2.25.RELEASE

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Certain Spring WebFlux applications may fail to enforce header-based routing checks during pre-flight requests. An unauthenticated network attacker could potentially bypass an intended authorization boundary, risking sensitive data, system changes, or disruption. Exposure requires a specific combination: affected Spring Framework versions, functional endpoints, and deployment with DispatcherServlet.

Executive priority

Treat as an immediate assessment and remediation priority for public-facing Java services. Direct teams to identify the required configuration combination first, then apply Spring-supported remediation. Escalate confirmed exposure where header predicates protect sensitive operations or data.

Technical view

CVE-2026-47892 is a CWE-863 authorization flaw affecting header predicates in pre-flight requests handled by WebFlux functional endpoints deployed with DispatcherServlet. Listed affected branches span Spring Framework 5.2.5.RELEASE through 7.0.8. The supplied CVSS 3.1 score is 9.8, reflecting unauthenticated, low-complexity network impact across confidentiality, integrity, and availability.

Likely exposure

Highest risk applies to internet-reachable applications combining an affected Spring version, WebFlux functional endpoints, DispatcherServlet deployment, and security-sensitive header predicates. Applications missing any required condition may be unaffected. The bundle does not establish how commonly this configuration occurs.

Exploitation context

The source bundle provides no evidence of active exploitation, and the CVE is not identified as being in KEV. However, the reported network reachability, lack of required privileges or user interaction, and low complexity make exposed deployments urgent to assess.

Researcher notes

The supplied record establishes affected version ranges and necessary deployment conditions but does not name fixed versions, technical root-cause details, proof-of-concept availability, or observed attacks. Default unaffected status suggests configurations outside the stated conditions should not be presumed vulnerable. Validate conclusions against the linked Spring advisory.

Mitigation direction

  • Inventory Spring Framework versions across deployed and packaged applications.
  • Identify applications combining WebFlux functional endpoints with DispatcherServlet.
  • Follow the Spring advisory for supported fixed releases or vendor-approved remediation.
  • Prioritize externally reachable applications using header predicates for security decisions.
  • Restrict unnecessary external access while remediation is evaluated and deployed.

Validation and detection

  • Confirm resolved Spring versions from build manifests, lockfiles, and packaged artifacts.
  • Review deployment configuration for DispatcherServlet and WebFlux functional endpoints.
  • Identify routes where header predicates influence authorization or sensitive processing.
  • Test pre-flight handling in an authorized staging environment after remediation.
  • Re-scan deployed artifacts to confirm affected versions are absent.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47892 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-47892Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SpringSpring Framework7.0.0, 6.2.0, 6.1.0, 6.0.0, 5.3.0, 5.2.5.RELEASEunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.