{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41005 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41005 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-41005 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-41005 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry CF Deployment. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41005/ (Markdown: https://insights.sbomify.com/CVE-2026-41005/index.md)","id":"CVE-2026-41005","markdown":"https://insights.sbomify.com/CVE-2026-41005/index.md","name":"CVE-2026-41005","record":{"aliases":["GHSA-wx8w-j86h-c458"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry UAA","requires_auth":"none","summary":"Attackers can bypass authentication in Cloud Foundry UAA by submitting encrypted but unsigned SAML assertions when signature verification is disabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"UAA accepts SAML Encrypted Assertions authentication bypass","id":"CVE-2026-41005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Spring HATEOAS Collection+JSON/UBER deserializers do not honor Jackson configuration","id":"CVE-2026-41006"},"packages":[],"prev":{"headline":"Spring Cloud Config Server Logged Sensitive Information","id":"CVE-2026-41004"},"products":["CF Deployment","UAA"],"published":"2026-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-13","vendors":["Cloud Foundry"]},"summary":"Attackers can bypass authentication in Cloud Foundry UAA by submitting encrypted but unsigned SAML assertions when signature verification is disabled.","url":"https://insights.sbomify.com/CVE-2026-41005/"}