{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-41005: UAA accepts SAML Encrypted Assertions authentication bypass","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-41005","status":"final","version":"1","initial_release_date":"2026-06-11T20:03:22.525Z","current_release_date":"2026-06-13T03:55:30.398Z","revision_history":[{"date":"2026-06-11T20:03:22.525Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"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.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-41005 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-41005"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-41005"},{"category":"external","summary":"cloudfoundry.org","url":"https://www.cloudfoundry.org/blog/cve-2026-41005-uaa-accepts-saml-encrypted-assertions-authentication-bypass/"}]},"product_tree":{"branches":[{"category":"vendor","name":"Cloud Foundry","branches":[{"category":"product_name","name":"UAA","branches":[{"category":"product_version_range","name":">=2.0.0 <78.14.0","product":{"name":"Cloud Foundry UAA >=2.0.0 <78.14.0","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:cloud_foundry:uaa:*:*:*:*:*:*:*:*"}}}]}]},{"category":"vendor","name":"Cloud Foundry","branches":[{"category":"product_name","name":"CF Deployment","branches":[{"category":"product_version_range","name":">=0.0.0 <57.0.0","product":{"name":"Cloud Foundry CF Deployment >=0.0.0 <57.0.0","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:cloud_foundry:cf_deployment:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-41005","title":"UAA accepts SAML Encrypted Assertions authentication bypass","notes":[{"category":"description","text":"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.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","baseScore":9,"baseSeverity":"CRITICAL"},"products":["CSAFPID-1","CSAFPID-2"]}],"remediations":[{"category":"vendor_fix","details":"Update to a fixed version: 57.0.0, 78.14.0.","product_ids":["CSAFPID-1","CSAFPID-2"]}]}]}