Skip to content
Fencer Intel
medium 6.5

CVE-2026-22723 json

UAA User Token Revocation logic error

published 8mo ago modified 4mo ago also GHSA-6wcw-r64p-qrrw , EUVD-2026-9877

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.cloudfoundry.identity:cloudfoundry-identity-server 78.8.0
  • cloudfoundry uaa-release 78.8.0

Is CVE-2026-22723 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.cloudfoundry.identity:cloudfoundry-identity-server
>=77.30.0, <78.8.0
78.8.0

Affected products

  • Cloudfoundry Foundation UAA

Classification

Weakness
  • CWE-693 Protection Mechanism Failure
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.