Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41003: An attacker able to influence values in RelyingPartyRegistration may be able to run arbitrary code on HTML for

29
Routine
HIGH 7.6UPGRADE

CVE-2026-41003 is a high-severity flaw (CVSS 7.6) affecting spring security. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.6 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionRequired
EPSS exploit chance0.2% (top 90%)
CISA exploited listNo
WeaknessCWE-79
Published2026-06-10
Last modified2026-07-23
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-07-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring security UPGRADE
Affected: >= 5.7.0 and < 5.7.24 · >= 5.8.0 and < 5.8.26 · >= 6.3.0 and < 6.3.17 · >= 6.4.0 and < 6.4.17 · >= 6.5.0 and < 6.5.10.2 · >= 7.0.0 and < 7.0.5.1
Fixed in: 5.7.24, 5.8.26, 6.3.17, 6.4.17, 6.5.10.2, 7.0.5.1
Safe to downgrade to: a release before 5.7.0
1. Check installed version
apt-cache policy spring-security || rpm -q spring-security || spring-security --version
2. UPGRADE to 5.7.24 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-security
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-security
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 5.7.0 (Debian / Ubuntu)
apt-cache madison spring-security sudo apt install spring-security=<VERSION_BEFORE_5.7.0> sudo apt-mark hold spring-security
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-security sudo dnf downgrade spring-security-<VERSION_BEFORE_5.7.0> sudo dnf versionlock add spring-security
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41003?

spring security: upgrade to 5.7.24, 5.8.26, 6.3.17, 6.4.17, 6.5.10.2, 7.0.5.1. Exact commands for each OS are on this page.

Is CVE-2026-41003 being exploited?

CVE-2026-41003 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41003 affect?

CVE-2026-41003 affects spring security. Severity is high (CVSS 7.6). 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 thr

How urgent is CVE-2026-41003?

Priority 29/100. High severity

Software pages

VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.