How severe is CVE-2018-15801?

CVE-2018-15801 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2018-15801 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-15801?

CVE-2018-15801 affects Vmware Spring Framework. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-15801?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2018-15801 published?

CVE-2018-15801 was published on 2018-12-19 and last updated on 2026-06-17.

CVE-2018-15801

CVE-2018-15801 is a high-severity vulnerability in Vmware Spring Framework with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: High (CVSS 3.x base score 7.4)
CVSS v2: 5.8
EPSS exploit prediction: 1% (47th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-345
Affected product: Vmware Spring Framework
Published: 2018-12-19
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2018-15801?: 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.
How severe is CVE-2018-15801?: CVE-2018-15801 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2018-15801 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-15801?: CVE-2018-15801 affects Vmware Spring Framework. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-15801?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-15801 published?: CVE-2018-15801 was published on 2018-12-19 and last updated on 2026-06-17.

References

https://pivotal.io/security/cve-2018-15801

Affected products (1)

cpe:2.3:a:vmware:spring_framework:*:*:*:*:*:*:*:*

More vulnerabilities in Vmware Spring Framework

CVE-2022-22965 — Critical (CVSS 9.8): A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data…
CVE-2016-1000027 — Critical (CVSS 9.8): Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java…
CVE-2018-1275 — Critical (CVSS 9.8): Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow…
CVE-2018-1270 — Critical (CVSS 9.8): Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow…
CVE-2015-5211 — Critical (CVSS 9.6): Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported…
CVE-2018-1258 — High (CVSS 8.8): Spring Framework version 5.0.5 when used in combination with any versions of Spring Security contains an authorization…

All CVEs affecting Vmware Spring Framework →

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-50214 — Critical (CVSS 9.8): The /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing…
CVE-2025-15385 — Critical (CVSS 9.8): Insufficient Verification of Data Authenticity vulnerability in TECNO Mobile com.Afmobi.Boomplayer allows…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →