CVE-2026-41003
Received Received - Intake
Code Execution in Spring Security HTML Forms

Publication date: 2026-06-10

Last updated on: 2026-06-10

Assigner: VMware

Description
An attacker able to influence values in RelyingPartyRegistration may be able to run arbitrary code on HTML forms generated by Spring Security filters. Affected versions: 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-10
Last Modified
2026-06-10
Generated
2026-06-10
AI Q&A
2026-06-10
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 6 associated CPEs
Vendor Product Version / Range
vmware spring_security From 5.7.0 (inc) to 5.7.23 (inc)
vmware spring_security From 5.8.0 (inc) to 5.8.25 (inc)
vmware spring_security From 6.3.0 (inc) to 6.3.16 (inc)
vmware spring_security From 6.4.0 (inc) to 6.4.16 (inc)
vmware spring_security From 6.5.0 (inc) to 6.5.10 (inc)
vmware spring_security From 7.0.0 (inc) to 7.0.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-41003 is a security vulnerability in Spring Security where unencoded HTML outputs may allow Cross-Site Scripting (XSS) attacks.

An attacker who can manipulate values in RelyingPartyRegistration could execute arbitrary code on HTML forms generated by Spring Security filters.

This means that if an attacker can influence certain input values, they might inject malicious scripts that run in the context of a user's browser.

Impact Analysis

This vulnerability can allow an attacker to run arbitrary code in the context of HTML forms generated by Spring Security filters.

Such Cross-Site Scripting (XSS) attacks can lead to theft of user credentials, session hijacking, or performing actions on behalf of the user without their consent.

The impact includes potential compromise of user data and loss of trust in the affected application.

Detection Guidance

Detection of this vulnerability involves identifying if your system is running an affected version of Spring Security where RelyingPartyRegistration values can be manipulated to execute arbitrary code on HTML forms.

You can check the version of Spring Security used in your application by inspecting your build configuration files or runtime environment.

  • For Maven projects, run: mvn dependency:list | grep spring-security
  • For Gradle projects, run: ./gradlew dependencies | grep spring-security

Additionally, monitoring HTTP responses for unencoded HTML output in forms generated by Spring Security filters may help detect exploitation attempts, but no specific commands for this are provided.

Mitigation Strategies

The primary mitigation step is to upgrade Spring Security to a fixed version that addresses this vulnerability.

  • Upgrade to one of the following versions depending on your current version: 5.7.24, 5.8.26, 6.3.17, 6.4.17, 6.5.11, or 7.0.6.

If upgrading immediately is not possible, consider applying any available patches through Enterprise Support if applicable.

Review and sanitize any inputs that influence RelyingPartyRegistration values to reduce the risk of arbitrary code execution.

Compliance Impact

The vulnerability in Spring Security allows an attacker to execute arbitrary code via Cross-Site Scripting (XSS) on HTML forms. Such a security flaw can potentially lead to unauthorized access or manipulation of sensitive data.

This type of vulnerability may impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information against unauthorized access and data breaches.

Organizations using affected versions of Spring Security should upgrade to fixed versions to mitigate risks and maintain compliance with these regulations.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-41003. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart