ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2016-5007

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…

Published May 25, 2017 · catalog updated Jun 17, 2026 · pivotal software spring framework

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2016-5007. EPSS is 2.80%. Act only if a listed version of pivotal software spring framework is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
2.80%
Remediation
Advisory link
Affected products
cpe pivotal software/spring framework · cpe vmware/spring framework

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe pivotal software/spring framework3.2.0
  • cpe pivotal software/spring framework4.0.0
  • cpe pivotal software/spring framework4.1.0
  • cpe pivotal software/spring framework4.2.0
  • cpe vmware/spring framework3.2.1
  • cpe vmware/spring framework3.2.2

How to fix CVE-2016-5007

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2016-5007. EPSS is 2.80%. Act only if a listed version of pivotal software spring framework is installed.

Which versions are affected?

Compare what you have installed with 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. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-264. EPSS 2.80%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Spring security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 25, 2017 · Monitored products — high

    Detected

    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 a

  2. Jun 17, 2026 · Monitored products — high

    Updated

    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 a

Sources

  • CVE.orgVulnerability recordCVE-2016-5007

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2016-5007

    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 a

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 7, 2026
  • CVE.orgNov 7, 2026