CVE-2016-4977

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 79% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS: 79%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
77(Track)
EG Risk 77/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation79% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.6%
KEV
Not listed

Published

May 25, 2017

Last Modified

May 13, 2026

Advisory Details (5)

Auto-updated May 22, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread.html/5e6dd946635bbcc9e1f2591599ad0fab54f2dc3714196af3b17893f2%40%3Cannounce.apache.org%3E
generic
https://lists.apache.org/thread.html/37d7e820fc65a768de3e096e98382d5529a52a039f093e59357d0bc0%40%3Cdev.fineract.apache.org%3E
generic
https://lists.apache.org/thread.html/0841d849c23418c473ccb9183cbf41a317cb0476e44be48022ce3488%40%3Cdev.fineract.apache.org%3E
generic

oss-security - Fwd: [CVE-2016-4977] Apache Fineract remote code execution vulnerabilities fixed in v1.3.0

http://www.openwall.com/lists/oss-security/2019/10/16/1
generic
https://lists.apache.org/thread.html/96c017115069408cec5e82ce1e6293facab398011f6db7e1befbe274%40%3Cdev.fineract.apache.org%3E

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.security.oauth:spring-security-oauth21.0.0.RELEASE, 1.0.1.RELEASE, 1.0.2.RELEASE, 1.0.3.RELEASE, 1.0.4.RELEASE1.0.5—

Data Freshness Timeline

(refreshed 6× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:23 UTCEG score recompute▲ 0.20
  2. 2026-07-22 22:02 UTCEG score recompute▼ 0.20
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-20 17:03 UTCEPSS rescore
  5. 2026-07-16 16:59 UTCEPSS rescore
  6. 2026-07-16 16:59 UTCEPSS rescore
  7. 2026-07-15 16:54 UTCEPSS rescore
  8. 2026-07-15 16:54 UTCEPSS rescore
  9. 2026-07-15 01:56 UTCEPSS rescore
  10. 2026-07-15 01:56 UTCEPSS rescore
  11. 2026-07-12 05:43 UTCEPSS rescore
  12. 2026-07-12 05:43 UTCEPSS rescore
  13. 2026-07-11 22:41 UTCOSV refresh
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-06 02:20 UTCEPSS rescore
  16. 2026-07-01 15:02 UTCEPSS rescore
  17. 2026-06-30 23:19 UTCEPSS rescore
  18. 2026-06-28 14:04 UTCEPSS rescore
  19. 2026-06-28 04:53 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 05:00 UTCOSV refresh
Show 20 more
  1. 2026-06-21 14:54 UTCEPSS rescore
  2. 2026-06-21 14:54 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-15 17:45 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-12 23:09 UTCEPSS rescore
  8. 2026-06-11 13:57 UTCEPSS rescore
  9. 2026-06-10 22:15 UTCEPSS rescore
  10. 2026-06-10 13:18 UTCEPSS rescore
  11. 2026-06-06 02:48 UTCOSV refresh
  12. 2026-06-04 13:10 UTCEPSS rescore
  13. 2026-06-04 13:10 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-24 16:43 UTCEPSS rescore
  17. 2026-05-22 13:03 UTCEG score recompute
  18. 2026-05-22 10:26 UTCOSV refresh
  19. 2026-05-18 21:30 UTCEPSS rescore
  20. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCtpt11fb/SpringVulScan
    First seen Jun 19, 2022

    burpsuite 的Spring漏洞扫描插件。SpringVulScan：支持检测：路由泄露|CVE-2022-22965|CVE-2022-22963|CVE-2022-22947|CVE-2016-4977

    Open source ↗
  • Nucleihttp/cves/2016/CVE-2016-4977.yaml
    First seen Jan 1, 2016

    Spring Security OAuth2 Remote Command Execution

    Open source ↗

Frequently asked(5)

What is CVE-2016-4977?
CVE-2016-4977 is a high vulnerability published on May 25, 2017. When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the responsetype parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for responsetype.
When was CVE-2016-4977 disclosed?
CVE-2016-4977 was first published in the National Vulnerability Database on May 25, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-4977 actively exploited?
CVE-2016-4977 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-4977?
CVE-2016-4977 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2016-4977?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-4977, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-4977

Explore →

Is Your Infrastructure Affected by CVE-2016-4977?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs