How severe is CVE-2016-5016?

CVE-2016-5016 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-5016?

CVE-2016-5016 affects the following packages: org.cloudfoundry.identity:cloudfoundry-identity-server (Maven), org.cloudfoundry.identity:cloudfoundry-identity-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-5016?

Update org.cloudfoundry.identity:cloudfoundry-identity-server to 3.3.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-5016 is resolved across your whole dependency graph.

How do I detect CVE-2016-5016 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cloudfoundry.identity:cloudfoundry-identity-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2016-5016 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2016-5016 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-5016 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2016-5016?

CVE-2016-5016 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2016-5016?

CVE-2016-5016 is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-5016 published, and has it been updated?

CVE-2016-5016 was published on April 24, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2016-5016 — cloudfoundry-identity-ser…

MEDIUMFix: cloudfoundry/uaa@0a78612

CVE-2016-5016 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in org.cloudfoundry.identity:cloudfoundry-identity-server. A fix is available for org.cloudfoundry.identity:cloudfoundry-identity-server — see the affected versions and patch details below.

Cloud Foundry vulnerable to Improper Certificate Validation

Also known asGHSA-rc2r-w8jv-vggp

Published

Apr 24, 2017

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Pivotal Cloud Foundry 239 and earlier, UAA (aka User Account and Authentication Server) 3.4.1 and earlier, UAA release 12.2 and earlier, PCF (aka Pivotal Cloud Foundry) Elastic Runtime 1.6.x before 1.6.35, and PCF Elastic Runtime 1.7.x before 1.7.13 does not validate if a certificate is expired.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 3.0.0&&< 3.3.0.3	3.3.0.3`org.cloudfoundry.identity:cloudfoundry-identity-server:3.3.0.3`
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 3.4.0&&< 3.4.2	3.4.2`org.cloudfoundry.identity:cloudfoundry-identity-server:3.4.2`

Affected Products

4 products · 5 configurations

Application

cloud foundrypivotal_software

≤ 239

range

Application

cloud foundry elastic runtimepivotal_software

≥ 1.7.0 && < 1.7.13

range

Application

cloud foundry uaapivotal_software

≤ 3.4.1

range

Application

cloud foundry uaa-releasepivotal_software

≤ 12.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cloudfoundry.identity:cloudfoundry-identity-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.cloudfoundry.identity:cloudfoundry-identity-server to 3.3.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-5016 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-5016 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-295CWE-295

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 24, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2016-5016

GHSA-rc2r-w8jv-vggp

References

Advisorygithub.com · v240 Advisorygithub.com · v11.3 Advisorygithub.com · v12.3 Advisorygithub.com · 2.7.4.6 Advisorygithub.com · 3.3.0.3 Advisorygithub.com · 3.4.2 Advisorypivotal.io · cve 2016 5016 Advisorynvd.nist.gov · CVE 2016 5016 Webgithub.com · 0a78612f981c541ad2d997e6a365f2a0b3e799d9 Webgithub.com · bc91ccd2029e8f1cea0c647f0c9aad4585f7a2c Webgithub.com · f97049df1c6c03effda5049c41704ac831ff3925

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting cloudfoundry-identity-server are rated as high or higher (top: critical).

CVE-2026-22723CVE-2018-1192CVE-2018-11041CVE-2018-15761CVE-2016-6637CVE-2018-1262CVE-2017-8032CVE-2017-4991

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2016-5016 — cloudfoundry-identity-ser…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2016-5016 in your dependencies?