Skip to content
Fencer Intel
high 7.5

CVE-2016-5007 json

Spring Security and Spring Framework may not recognize certain paths that should be protected

published 2017-05-25 9 y ago modified 2026-06-17 4 mo ago also GHSA-8crv-49fr-2h6j , EUVD-2018-0549

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework:spring-core 4.3.1
  • maven org.springframework.security:spring-security-core 4.1.1
  • libspring-java Debian 14, Debian 13, Debian 12 4.3.2-1

debian advisories DEBIAN-CVE-2016-5007

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-5007 updated cvss 5.3

spring: Path matching inconsistency

  • Red Hat JBoss A-MQ 6 karaf karaf Red Hat JBoss Fuse 6 Karaf Karaf
    affected: no fix available
  • Red Hat Enterprise Virtualization 3 rhevm-dependencies, jasperreports-server-pro, redhat-support-plugin-rhev Red Hat OpenShift Enterprise 2 spring-core, spring-security-core
    under investigation

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework:spring-core
<4.3.1
4.3.1
maven org.springframework.security:spring-security-core
<4.1.1
4.1.1

Affected products

  • Pivotal Spring Security
  • Pivotal Spring Framework

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.