CVE-2026-22752

Analyzed Analyzed - Analysis Complete

Authentication Bypass in Spring Authorization Server

Publication date: 2026-07-16

Last updated on: 2026-09-04

Assigner: VMware

Description

Authentication bypass by primary weakness vulnerability in Spring Security Spring Authorization Server. This issue affects Spring Authorization Server: from 7.0.0 through 7.0.4, from 1.5.0 through 1.5.6, from 1.4.0 through 1.4.9, from 1.3.0 through 1.3.10.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-16

Last Modified

2026-09-04

Generated

2026-09-15

AI Q&A

2026-07-16

EPSS Evaluated

2026-09-13

NVD

CVE-2026-22752

EUVD

EUVD-2026-44904

Affected Vendors & Products

Vendor	Product	Version / Range
broadcom	spring_authorization_server	From 1.3.0 (inc) to 1.3.11 (exc)
broadcom	spring_authorization_server	From 1.4.0 (inc) to 1.4.10 (exc)
broadcom	spring_authorization_server	From 1.5.0 (inc) to 1.5.7 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-287	When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Attack-Flow Graph

Executive Summary

This vulnerability is an authentication bypass issue in Spring Security's Spring Authorization Server. It occurs due to insufficient validation of client metadata fields in Dynamic Client Registration endpoints when explicitly enabled. An attacker with a valid Initial Access Token can register a malicious client with crafted metadata, potentially leading to attacks like XSS, privilege escalation, or SSRF depending on server configuration.

Detection Guidance

Check if your Spring Authorization Server version falls within the affected ranges (7.0.0-7.0.4, 1.5.0-1.5.6, 1.4.0-1.4.9, 1.3.0-1.3.10). Verify if Dynamic Client Registration endpoints are enabled and if client metadata validation is insufficient.

Impact Analysis

An attacker could exploit this to perform actions like XSS attacks, gain elevated privileges, or execute server-side requests forgery. This could lead to unauthorized access, data breaches, or system compromise if the server is configured to allow such metadata fields.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, which may violate compliance requirements under GDPR (data protection) or HIPAA (healthcare data privacy). Organizations must address it to maintain regulatory compliance and protect sensitive data.

Mitigation Strategies

Upgrade to fixed versions: 7.0.5 (OSS), 1.5.7 (OSS), 1.4.10 (Enterprise-only), or 1.3.11 (Enterprise-only). No additional mitigation is required after upgrading.

Hi! I’m here to help you understand CVE-2026-22752. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70