{“lastseen”:””,”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.\\n\\nAffected versions:\\nCloud Foundry UAA (uaa_release) 2.0.0 through 78.13.0.\\nCloud Foundry CF Deployment all versions through 56.1.0.”,”published”:”2026-06-11T20:03:22.525Z”,”modified”:”2026-06-11T20:03:22.525Z”,”type”:”cve”,”title”:”UAA accepts SAML Encrypted Assertions authentication bypass”,”source”:”vmware”,”references”:”https:\/\/www.cloudfoundry.org\/blog\/cve-2026-41005-uaa-accepts-saml-encrypted-assertions-authentication-bypass\/”,”id”:”CVE-2026-41005″,”bulletinFamily”:””,”cwe”:[“CWE-347″],”cvelist”:null,”sourceData”:”Cloud Foundry UAA 2.0.0\\nCloud Foundry CF Deployment 0.0.0″,”sourceHref”:””,”cvss”:{“score”:9,”severity”:”CRITICAL”,”vector”:”CVSS:3.1\/AV:N\/AC:H\/PR:N\/UI:N\/S:C\/C:H\/I:H\/A:H”,”version”:”3.1″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”UAA”,”version”:”2.0.0″,”vendor”:”Cloud Foundry”,”ai_description”:”UAA accepts SAML encrypted assertions, allowing authentication bypass due to incorrect treatment of XML encryption as a substitute for XML signatures”,”ai_severity”:”Critical”,”ai_vendor”:”Cloud Foundry”,”ai_product”:”Cloud Foundry UAA”,”ai_version”:”2.0.0-78.13.0″,”ai_score”:9}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”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…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[9,6,8,86,12,13,7,11,5],"class_list":["post-62052","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-critical","tag-cve","tag-cvss","tag-cvss-90","tag-exploit","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n