CVE-2026-41003: VMware Spring Security XSS in RelyingPartyRegistration

CVE-2026-41003 · Severity: high · CVSS 7.6 · Published 2026-06-10

A vulnerability in Spring Security's SAML2 component could allow an attacker to execute malicious code within a user's browser. This occurs when the system generates HTML forms using data that an attacker has influenced, such as SAML registration details. If exploited, this could lead to the theft of sensitive user information or unauthorized actions performed on behalf of the user.

Technologies: org.springframework.security:spring-security-saml2-service-provider (Maven), VMware Spring Security. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41003 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41003 being exploited in the wild.
How severe is CVE-2026-41003?
High severity, with a CVSS score of 7.6, published 10 June 2026.
Which products and versions are affected?
org.springframework.security:spring-security-saml2-service-provider (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.6; VMware Spring Security 5.7.0 through 5.7.23; 5.8.0 through 5.8.25; 6.3.0 through 6.3.16; 6.4.0 through 6.4.16; 6.5.0 through 6.5.10; 7.0.0 through 7.0.5.
Is there a fix for CVE-2026-41003?
Yes. org.springframework.security:spring-security-saml2-service-provider (Maven): upgrade to 7.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41003 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41003?
Check whether you run org.springframework.security:spring-security-saml2-service-provider (Maven) or VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.security:spring-security-saml2-service-provider (Maven): upgrade to 7.0.6 or later
    # set org.springframework.security:spring-security-saml2-service-provider to 7.0.6 in your pom.xml or build.gradle

Technical details

A Cross-Site Scripting (XSS) vulnerability exists in the Spring Security SAML2 Service Provider. The root cause is the improper neutralization of input within the RelyingPartyRegistration component when generating HTML forms via Spring Security filters. Specifically, the FormPostRedirectStrategy failed to properly handle or encode values, allowing an attacker who can influence registration metadata to inject malicious scripts into hidden form inputs. An attacker with low privileges could leverage this to execute arbitrary JavaScript in the context of a victim's browser session. Patches are available in versions 6.5.11 and 7.0.6.

Affected products

  • Spring Spring Security SAML2 Service Provider 5.7.0 to 5.7.23, 5.8.0 to 5.8.25, 6.3.0 to 6.3.16, 6.4.0 to 6.4.16, 6.5.0 to 6.5.10, 7.0.0 to 7.0.5

Identifiers

  • CVE-2026-41003
  • GHSA-3pjj-qpw6-5fcm

Timeline

  • 2026-06-10: disclosed
  • 2026-06-10: advisory
  • 2026-06-09: patched: Release of version 6.5.11

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.