# CVE-2026-22734: Cloud Foundry UAA SAML 2.0 Signature Bypass

> Attackers can bypass SAML signature validation to obtain tokens for any user and access protected systems when SAML bearer assertions are enabled.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2026
- **Updated:** 17 Apr 2026
- **Also known as:** GHSA-vp68-f85j-5gw3

## What is CVE-2026-22734?

CVE-2026-22734 is a high-severity authentication bypass vulnerability in Cloud Foundry UUA, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloud Foundry UUA is vulnerable to a bypass that allows an attacker to obtain a token for any user and gain access to UAA-protected systems. This vulnerability exists when SAML 2.0 bearer assertions are enabled for a client, as the UAA accepts SAML 2.0 bearer assertions that are neither signed nor encrypted. This issue affects UUA from v77.30.0 to v78.7.0 (inclusive) and it affects CF Deployment from v48.7.0 to v54.14.0 (inclusive).

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

No fix has been published for CVE-2026-22734 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22734 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22734 is a high-severity authentication bypass vulnerability in Cloud Foundry UUA, published on 16 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22734 in the wild and no public exploit code.

Affected product: Cloud Foundry UUA. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-22734/ (Markdown: https://insights.sbomify.com/CVE-2026-22734/index.md)
```

## Sources

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

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