CVE-2026-59354: VMware Spring Security privilege escalation (CVSS 9.6)

Description

In versions of Spring Security's OAuth2 Authorization Server module 7.0.0 through 7.0.4, when Dynamic Client Registration is explicitly enabled, the registration endpoint performs insufficient validation of certain client metadata fields supplied by the registering client. An attacker who possesses a valid Initial Access Token can register a malicious client with crafted metadata, which, depending on server configuration and how the metadata is later rendered or used, may result in Stored Cross-Site Scripting (XSS), Privilege Escalation, or Server-Side Request Forgery (SSRF).

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

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

Affected products

VMware Spring Security≥ 7.0.0 < 7.0.5

Remediation

Fixed in

VMware Spring Security≥ 7.0.5

Patch & vendor advisories

https://spring.io/security/cve-2026-59354

References

https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N&version=3.1US Government ResourceThird Party Advisory
https://spring.io/security/cve-2026-59354Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-59354 being actively exploited?

CVE-2026-59354 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.

How severe is CVE-2026-59354?

CVE-2026-59354 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.49% probability of exploitation.

Which products are affected by CVE-2026-59354?

Affected products include VMware Spring Security.

How do I fix CVE-2026-59354?

Upgrade affected software to a fixed version, for example VMware Spring Security 7.0.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-59354 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo