# CVE-2026-41005: UAA accepts SAML Encrypted Assertions authentication bypass

> Attackers can bypass authentication in Cloud Foundry UAA by submitting encrypted but unsigned SAML assertions when signature verification is disabled.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** GHSA-wx8w-j86h-c458

## What is CVE-2026-41005?

CVE-2026-41005 is a critical authentication bypass vulnerability in Cloud Foundry CF Deployment, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloud Foundry UAA incorrectly treated XML encryption to the Service Provider (confidentiality) as a substitute for XML signatures from the Identity Provider (authenticity) in two SAML flows: the OAuth 2.0 SAML2 bearer grant (token endpoint) and browser SSO (ACS) when wantAssertionSigned is set to false. Assertions or responses that were unsigned but contained encrypted content could still be accepted. Encryption uses the SP's public key from published metadata, therefore, any party, not only a trusted IdP, can produce ciphertext UAA can decrypt; successful decryption therefore does not prove the IdP issued the message.

Affected versions:
Cloud Foundry UAA (uaa_release) 2.0.0 through 78.13.0.
Cloud Foundry CF Deployment all versions through 56.1.0.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-41005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41005 is a critical authentication bypass vulnerability in Cloud Foundry CF Deployment, published on 11 Jun 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-41005 in the wild and no public exploit code.

Affected product: Cloud Foundry CF Deployment. 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-41005/ (Markdown: https://insights.sbomify.com/CVE-2026-41005/index.md)
```

## Sources

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

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