CVE-2016-6651
No exploitation reported by the sources we read.
- Published2016-09-30
- WeaknessCWE-264
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The UAA /oauth/token endpoint in Pivotal Cloud Foundry (PCF) before 243; UAA 2.x before 2.7.4.8, 3.x before 3.3.0.6, and 3.4.x before 3.4.5; UAA BOSH before 11.7 and 12.x before 12.6; Elastic Runtime before 1.6.40, 1.7.x before 1.7.21, and 1.8.x before 1.8.2; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 allows remote authenticated users to gain privileges by leveraging possession of a token.
Timeline
dates in UTC- 2016-09-3000:59CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-6651?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-6651?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.6 | = 1.6.0 | no fix published | NVD |
| 1.6 | = 1.6.1 | no fix published | NVD |
| 1.6 | = 1.6.2 | no fix published | NVD |
| 1.6 | = 1.6.3 | no fix published | NVD |
| 1.6 | = 1.6.4 | no fix published | NVD |
| 1.6 | = 1.6.5 | no fix published | NVD |
| 1.6 | = 1.6.6 | no fix published | NVD |
| 1.6 | = 1.6.7 | no fix published | NVD |
| 1.6 | = 1.6.8 | no fix published | NVD |
| 1.6 | = 1.6.9 | no fix published | NVD |
| 1.6 | = 1.6.10 | no fix published | NVD |
| 1.6 | = 1.6.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.7 | = 1.7.0 | no fix published | NVD |
| 1.7 | = 1.7.1 | no fix published | NVD |
| 1.7 | = 1.7.2 | no fix published | NVD |
| 1.7 | = 1.7.3 | no fix published | NVD |
| 1.7 | = 1.7.4 | no fix published | NVD |
| 1.7 | = 1.7.5 | no fix published | NVD |
| 1.7 | = 1.7.6 | no fix published | NVD |
| 1.7 | = 1.7.7 | no fix published | NVD |
| 1.7 | = 1.7.8 | no fix published | NVD |
| 1.7 | = 1.7.9 | no fix published | NVD |
| 1.7 | = 1.7.10 | no fix published | NVD |
| 1.7 | = 1.7.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | ≤ 16.0 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- pivotal.ioMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.06.5read 2026-10-23
- NVDweakness (CWE)CWE-264read 2026-10-23
- FIRST EPSSEPSS score1.7 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-09-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-6651?
Is CVE-2016-6651 actively exploited?
What is the CVSS score for CVE-2016-6651?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.