# CVE-2016-5007: Spring Security and Spring Framework may not recognize certain paths that should be protected

Source: https://junglewise.ai/threats/cve-2016-5007-spring-security-and-spring-framework-may-not-recognize-certain  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2018-10-17  
License: CC BY 4.0 with a link back

CVE-2016-5007 · Severity: low · CVSS 3 · Published 2018-10-17

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

Technologies: [org.springframework:spring-core (Maven)](https://junglewise.ai/threats/technologies/org-springframework-spring-core), [org.springframework.security:spring-security-core (Maven)](https://junglewise.ai/threats/technologies/org-springframework-security-spring-security-core). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2016-5007 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2016-5007 being exploited in the wild.

**How severe is CVE-2016-5007?** Low severity, with a CVSS score of 3, published 17 October 2018.

**Which products and versions are affected?** org.springframework:spring-core (Maven) ECOSYSTEM:introduced=0,fixed=4.3.1; org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=4.1.1.

**Is there a fix for CVE-2016-5007?** Yes. org.springframework:spring-core (Maven): upgrade to 4.3.1 or later; org.springframework.security:spring-security-core (Maven): upgrade to 4.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2016-5007?** Check whether you run org.springframework:spring-core (Maven) or org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.springframework:spring-core (Maven): upgrade to 4.3.1 or later

  ```sh
  # set org.springframework:spring-core to 4.3.1 in your pom.xml or build.gradle
  ```

- org.springframework.security:spring-security-core (Maven): upgrade to 4.1.1 or later

  ```sh
  # set org.springframework.security:spring-security-core to 4.1.1 in your pom.xml or build.gradle
  ```


## Affected products

- org.springframework:spring-core (Maven) ECOSYSTEM:introduced=0,fixed=4.3.1
- org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=0,fixed=4.1.1

## Identifiers

- CVE-2016-5007
- GHSA-8crv-49fr-2h6j

## Related threats

- [VMware Spring Framework ReDoS in AntPathMatcher](https://junglewise.ai/threats/cve-2026-41848-vmware-spring-framework-redos-in-antpathmatcher)
- [Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider](https://junglewise.ai/threats/cve-2026-22746-spring-security-vulnerable-to-user-attribute-enumeration-when)
- [Spring Spring Security TOCTOU race condition in JdbcOneTimeTokenService](https://junglewise.ai/threats/cve-2026-22751-spring-spring-security-toctou-race-condition-in)
- [Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide](https://junglewise.ai/threats/cve-2025-22234-spring-security-has-a-broken-timing-attack-mitigation-implemented)
- [Spring Security annotation detection mechanism has authorization bypass](https://junglewise.ai/threats/cve-2025-41248-spring-security-annotation-detection-mechanism-has-authorization)