CVE-2018-15801
mediumpriority · track · 30OT risk · elevatedEPSS 0.007 · 51 %ileEUUSEPSS · scored 2026-10-27
Spring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–high · 3.3–7.4
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
- Maven org.springframework.security:spring-security-core5.1.0 → 5.1.2osvUSpkg:maven/org.springframework.security/spring-security-core
- Maven org.springframework.security:spring-security-oauth2-jose5.1.0 → 5.1.2osvUSpkg:maven/org.springframework.security/spring-security-oauth2-jose
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-27xw-p8v6-9jjrSpring Security vulnerable to Authorization Bypass2018-12-20ghsa · osvUS
Spring Security versions 5.1.x prior to 5.1.2 contain an authorization bypass vulnerability during JWT issuer validation. In order to be impacted, the same private key for an honest issuer and a malicious user must be used when signing JWTs. In that case, a malicious user could fashion signed JWTs with the malicious issuer URL that may be granted for the honest issuer.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (3)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan