CVE-2026-41005: CWE-347: Improper Verification of Cryptographic Signature in Cloud Foundry UAA
Cloud Foundry UAA versions 2.0.0 through 78.13.0 have a vulnerability where XML encryption is incorrectly used as a substitute for XML signature verification in certain SAML flows. This flaw allows unsigned assertions or responses containing encrypted content to be accepted, as successful decryption does not prove authenticity. The vulnerability affects OAuth 2.0 SAML2 bearer grant and browser SSO flows when wantAssertionSigned is set to false.
AI Analysis
Technical Summary
CVE-2026-41005 is an improper verification of cryptographic signature vulnerability (CWE-347) in Cloud Foundry UAA. The product incorrectly treats XML encryption to the Service Provider as a substitute for XML signatures from the Identity Provider in two SAML flows: OAuth 2.0 SAML2 bearer grant and browser SSO (ACS) when wantAssertionSigned is false. Because encryption uses the Service Provider's public key, any party can produce ciphertext that UAA can decrypt, so successful decryption does not guarantee the message was issued by a trusted Identity Provider. This allows acceptance of unsigned assertions or responses containing encrypted content, undermining authenticity guarantees.
Potential Impact
An attacker can craft unsigned SAML assertions or responses with encrypted content that UAA will accept as authentic, potentially allowing unauthorized access or impersonation in affected SAML flows. The vulnerability impacts confidentiality, integrity, and availability as indicated by the CVSS vector. This compromises the trust model of authentication and authorization in Cloud Foundry UAA deployments using these SAML flows with wantAssertionSigned set to false.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Until a fix is available, administrators should consider enforcing wantAssertionSigned=true in SAML configurations to require signed assertions or responses, thereby avoiding reliance on encryption as a substitute for signature verification.
CVE-2026-41005: CWE-347: Improper Verification of Cryptographic Signature in Cloud Foundry UAA
Description
Cloud Foundry UAA versions 2.0.0 through 78.13.0 have a vulnerability where XML encryption is incorrectly used as a substitute for XML signature verification in certain SAML flows. This flaw allows unsigned assertions or responses containing encrypted content to be accepted, as successful decryption does not prove authenticity. The vulnerability affects OAuth 2.0 SAML2 bearer grant and browser SSO flows when wantAssertionSigned is set to false.
CVSS v3.1
Score 9.0critical
Affected software
pkg:github/cloudfoundry/uaa_releaseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41005 is an improper verification of cryptographic signature vulnerability (CWE-347) in Cloud Foundry UAA. The product incorrectly treats XML encryption to the Service Provider as a substitute for XML signatures from the Identity Provider in two SAML flows: OAuth 2.0 SAML2 bearer grant and browser SSO (ACS) when wantAssertionSigned is false. Because encryption uses the Service Provider's public key, any party can produce ciphertext that UAA can decrypt, so successful decryption does not guarantee the message was issued by a trusted Identity Provider. This allows acceptance of unsigned assertions or responses containing encrypted content, undermining authenticity guarantees.
Potential Impact
An attacker can craft unsigned SAML assertions or responses with encrypted content that UAA will accept as authentic, potentially allowing unauthorized access or impersonation in affected SAML flows. The vulnerability impacts confidentiality, integrity, and availability as indicated by the CVSS vector. This compromises the trust model of authentication and authorization in Cloud Foundry UAA deployments using these SAML flows with wantAssertionSigned set to false.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Until a fix is available, administrators should consider enforcing wantAssertionSigned=true in SAML configurations to require signed assertions or responses, thereby avoiding reliance on encryption as a substitute for signature verification.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:19:16.426Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2b1e56815e7002b82d6ae7
Added to database: 6/11/2026, 8:45:10 PM
Last enriched: 6/11/2026, 9:00:09 PM
Last updated: 6/11/2026, 10:08:36 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.