# CVE-2026-22723: UAA User Token Revocation logic error

> Attackers can bypass token revocation mechanisms due to a logic error, maintaining unauthorized access to Cloud Foundry UAA services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2026
- **Updated:** 10 May 2026
- **Also known as:** GHSA-6wcw-r64p-qrrw

## What is CVE-2026-22723?

CVE-2026-22723 is a medium-severity vulnerability in Cloudfoundry Foundation UAA, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Inappropriate user token revocation due to a logic error in the token revocation endpoint implementation in Cloudfoundry UAA v77.30.0 to v78.7.0 and in Cloudfoundry Deployment v48.7.0 to v54.10.0.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2026-22723?

2 open source packages ship an affected version, including org.cloudfoundry.identity:cloudfoundry-identity-server. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 77.30.0 | 78.8.0 |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 77.30.0 | 78.8.0 |

Products: Cloudfoundry Cf-Deployment, Cloudfoundry Uaa-Release.

## How do I fix CVE-2026-22723?

Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 78.8.0 or later.

## Is CVE-2026-22723 being exploited?

There is no known exploitation of CVE-2026-22723 in the wild and no public exploit code.

## Other vulnerabilities in Cloudfoundry Foundation UAA

- [CVE-2022-31733](https://insights.sbomify.com/CVE-2022-31733/): Auth bypass in Cloud Foundry Diego and CF Deployment (critical 9.1)
- [CVE-2020-5402](https://insights.sbomify.com/CVE-2020-5402/): UAA fails to check the state parameter when authenticating with external IDPs (high 8.8)
- [CVE-2019-11293](https://insights.sbomify.com/CVE-2019-11293/): UAA logs all query parameters with debug logging level (high 8.8)
- [CVE-2019-11290](https://insights.sbomify.com/CVE-2019-11290/): Cloud Foundry UAA logs query parameters in tomcat access file (high 8.8)
- [CVE-2019-11283](https://insights.sbomify.com/CVE-2019-11283/): Password leak in smbdriver logs (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22723 and fix it if it is affected.

What it is: CVE-2026-22723 is a medium-severity vulnerability in Cloudfoundry Foundation UAA, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22723 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 77.30.0; fixed in 78.8.0
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 77.30.0; fixed in 78.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22723/ (Markdown: https://insights.sbomify.com/CVE-2026-22723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22723
- OSV: https://osv.dev/vulnerability/CVE-2026-22723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22723/
Summaries are generated and may contain mistakes; the official description above is the record.