CVE-2016-8218

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

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

An issue was discovered in Cloud Foundry Foundation routing-release versions prior to 0.142.0 and cf-release versions 203 to 231. Incomplete validation logic in JSON Web Token (JWT) libraries can allow unprivileged attackers to impersonate other users to the routing API, aka an "Unauthenticated JWT signing algorithm in routing" issue.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
66.9%
KEV
Not listed

Published

June 13, 2017

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

CVE-2016-8218: Unauthenticated JWT signing algorithm in routing | Cloud Foundry

https://www.cloudfoundry.org/cve-2016-8218/

Frequently asked(5)

What is CVE-2016-8218?
CVE-2016-8218 is a critical vulnerability published on June 13, 2017. An issue was discovered in Cloud Foundry Foundation routing-release versions prior to 0.142.0 and cf-release versions 203 to 231. Incomplete validation logic in JSON Web Token (JWT) libraries can allow unprivileged attackers to impersonate other users to the routing API, aka an "Unauthenticated JWT…
When was CVE-2016-8218 disclosed?
CVE-2016-8218 was first published in the National Vulnerability Database on June 13, 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-8218 actively exploited?
CVE-2016-8218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 66.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-8218?
CVE-2016-8218 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-8218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8218, 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

Explore the affected products and dependency analysis for CVE-2016-8218

Explore →

Is Your Infrastructure Affected by CVE-2016-8218?

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