CVE-2020-5407: Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerabil

This month

HIGH 8.8UPGRADE

CVE-2020-5407 is a high-severity flaw (CVSS 8.8) affecting spring security. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Weakness	CWE-347
Published	2020-05-13
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: pivotal software

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-05-13 17:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

pivotal software spring security UPGRADE

Affected: >= 5.2.0 and < 5.2.4 · >= 5.3.0 and < 5.3.2

Fixed in: 5.2.4, 5.3.2

Safe to downgrade to: a release before 5.2.0

1. Check installed version

apt-cache policy spring-security || rpm -q spring-security || spring-security --version

2. UPGRADE to 5.2.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-security

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-security

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.2.0 (Debian / Ubuntu)

apt-cache madison spring-security sudo apt install spring-security=<VERSION_BEFORE_5.2.0> sudo apt-mark hold spring-security

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-security sudo dnf downgrade spring-security-<VERSION_BEFORE_5.2.0> sudo dnf versionlock add spring-security

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5407?

spring security: upgrade to 5.2.4, 5.3.2. Exact commands for each OS are on this page.

Is CVE-2020-5407 being exploited?

CVE-2020-5407 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5407 affect?

CVE-2020-5407 affects spring security. Severity is high (CVSS 8.8). Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can careful

How urgent is CVE-2020-5407?

Priority 48/100. High severity

Related CVEs

CVE-2026-22754 HIGH 7.5 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22753 HIGH 7.5 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22747 MEDIUM 6.8 UPGRADE Vulnerability in Spring Spring Security. SubjectX500PrincipalExtractor does not correctly handle certain malfo
CVE-2026-22746 LOW 3.7 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22751 MEDIUM 4.8 UPGRADE Vulnerability in Spring Spring Security

References

← Back to latest CVEs