CVE-2018-15801: Spring Security Authorization Bypass

Summary

20/12/2018
Yes i
High
7.4

CVE-2018-15801: Spring Security vulnerable to Authorization Bypass. Affects org.springframework.security:spring-security-core versions >= 5.1.0, < 5.1.2. Fixed in 5.1.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Spring Security package is a widely used library for implementing security features in Java applications. It provides authentication and authorization mechanisms to protect sensitive resources. This vulnerability affects versions 5.1.x of the Spring Security Core and Spring Security OAuth2 Jose packages. These packages are commonly used in Maven-based projects.

Vulnerability Detail

The vulnerability in Spring Security versions 5.1.x prior to 5.1.2 allows for an authorization bypass during JWT issuer validation. If the same private key is used for both an honest issuer and a malicious user when signing JWTs, the malicious user can create signed JWTs with the malicious issuer URL. These JWTs may be granted access as if they were issued by the honest issuer. This can lead to unauthorized access to sensitive resources.

How To Fix

Latest published version: 7.2.0-RC1 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed versions of the affected packages.

Conclusion

The CVE-2018-15801 vulnerability in Spring Security versions 5.1.x prior to 5.1.2 allows for an authorization bypass, potentially leading to unauthorized access to sensitive resources. It is crucial to upgrade to the fixed versions of the affected packages (5.1.2 or later) to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.springframework.security:spring-security-core →

Share this vulnerability

FAQ

This vulnerability allows an attacker to bypass authorization checks and gain unauthorized access to sensitive resources.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

No, only versions 5.1.x prior to 5.1.2 are affected. It is recommended to upgrade to the fixed version.

There is no known public exploit for this vulnerability at the time of this report. However, it is crucial to patch your application to prevent any potential exploitation.

You can find more details about this vulnerability, including the CVE identifier, in the GitHub Advisory Database at the following link: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/12/GHSA-27xw-p8v6-9jjr/GHSA-27xw-p8v6-9jjr.json

Related vulnerabilities

Recent vulnerabilities recorded for org.springframework.security:spring-security-core.

How To Fix

Latest published version: 7.2.0-RC1 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback