CVE-2016-5007

What it is

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering.

Exploit odds

2.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-05-25 17:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:48 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.8% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-05-25 17:29 UTC

Last modified

2026-06-17 00:48 UTC

Exploit probability

2.8% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Pivotal Software Spring Framework 3.2.0
• Pivotal Software Spring Framework 4.0.0
• Pivotal Software Spring Framework 4.1.0
• Pivotal Software Spring Framework 4.2.0
• VMware Spring Framework 3.2.1
• VMware Spring Framework 3.2.2
• VMware Spring Framework 3.2.3
• VMware Spring Framework 3.2.4

Attack profile CVSS 3.0 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-5007.md and follow it. Check whether this project is affected by CVE-2016-5007. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge