{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-40965 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40965 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40965 is a critical vulnerability in Cloud Foundry Foundation CF Deployment, published on 1 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-40965 and fix it if it is affected.\n\nWhat it is: CVE-2026-40965 is a critical vulnerability in Cloud Foundry Foundation CF Deployment, published on 1 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-40965 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry Foundation 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-40965/ (Markdown: https://insights.sbomify.com/CVE-2026-40965/index.md)","id":"CVE-2026-40965","markdown":"https://insights.sbomify.com/CVE-2026-40965/index.md","name":"CVE-2026-40965","record":{"aliases":["GHSA-qc5f-2h9q-7m2g"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry UAA","requires_auth":"none","summary":"Attackers can extract EC private keys from the public token_keys endpoint, enabling JWT forgery and authentication bypass in Cloud Foundry deployments using EC keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a vulnerability where EC (Elliptic Curve) private keys are inadvertently exposed through the public /token_keys endpoint. This endpoint is designed to provide public key material for JWT token verification but incorrectly exposes private key components for EC keys. The vulnerability affects deployments using EC keys for JWT token signing. The vulnerability does not affect RSA key configurations, only deployments using EC keys for JWT signing.\n\nAffected versions:\n- uaa_release: v76.12.0 through v78.12.0 (inclusive); fixed in v78.13.0 or later\n- CF Deployment: v30.0.0 through v56.0.0 (inclusive); fixed in v56.1.0 or later (bundles uaa_release v78.13.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":"Information disclosure in CF Deployment","id":"CVE-2026-40965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration","id":"CVE-2026-40966"},"packages":[],"prev":{"headline":"Auth bypass in CF Deployment","id":"CVE-2026-40964"},"products":["CF Deployment","uaa_release"],"published":"2026-06-01","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-03","vendors":["Cloud Foundry Foundation"]},"summary":"Attackers can extract EC private keys from the public token_keys endpoint, enabling JWT forgery and authentication bypass in Cloud Foundry deployments using EC keys.","url":"https://insights.sbomify.com/CVE-2026-40965/"}