How severe is CVE-2018-11047?

CVE-2018-11047 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix CVE-2018-11047?

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

How do I detect CVE-2018-11047 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-2018-11047 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2018-11047 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-11047 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-2018-11047?

CVE-2018-11047 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-2018-11047?

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

When was CVE-2018-11047 published, and has it been updated?

CVE-2018-11047 was published on July 24, 2018 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

HIGH severity

CVE-2018-11047 — cloudfoundry-identity-ser…

HIGHFix: cloudfoundry/uaa@0cd3c6f

CVE-2018-11047 is a high-severity (CVSS 7.5) CWE-863 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 UAA accepts refresh token as access token on admin endpoints

Also known asGHSA-r4v8-9hgx-vm6m

Published

Jul 24, 2018

Updated

Oct 24, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% 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

5 pkgs affected

☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server☕org.cloudfoundry.identity:cloudfoundry-identity-server☕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

Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. This affects the administrative endpoints of the UAA. i.e. /Users, /Groups, etc. However, if the user has been deleted or had groups removed, or the client was deleted, the refresh token will no longer be valid.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	all versions	4.5.7`org.cloudfoundry.identity:cloudfoundry-identity-server:4.5.7`
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.6.0&&< 4.7.6	4.7.6`org.cloudfoundry.identity:cloudfoundry-identity-server:4.7.6`
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.8.0&&< 4.10.2	4.10.2`org.cloudfoundry.identity:cloudfoundry-identity-server:4.10.2`
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.11.0&&< 4.12.4	4.12.4`org.cloudfoundry.identity:cloudfoundry-identity-server:4.12.4`
☕Maven	`org.cloudfoundry.identity:cloudfoundry-identity-server`	≥ 4.13.0&&< 4.19.2	4.19.2`org.cloudfoundry.identity:cloudfoundry-identity-server:4.19.2`

Affected Products

1 product · 5 configurations

Application

cloud foundry uaapivotal_software

≥ 4.19.0 && < 4.19.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 4.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11047 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-11047 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works