PT-2026-48733 · Cloud Foundry · Cf-Deployment+1

Published 2026-06-11 · Updated 2026-06-11 · CVE-2026-41005

Mitre

CVSS v3.1

9.0

Critical

Base vector

AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

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.

Fix

Improper Verification of Cryptographic Signature

Weakness Enumeration

CWE-347

Related Identifiers

CVE-2026-41005

Affected Products

Cf-Deployment

Uaa

References · 2

• https://nvd.nist.gov/vuln/detail/CVE-2026-41005 · Security Note
• https://cloudfoundry.org/blog/cve-2026-41005-uaa-accepts-saml-encrypted-assertions-authentication-bypass · Note