{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61779 exists.","fix":"No fix has been published for CVE-2025-61779 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61779 is a high-severity missing authorization vulnerability in confidential-containers trustee, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61779 and fix it if it is affected.\n\nWhat it is: CVE-2025-61779 is a high-severity missing authorization vulnerability in confidential-containers trustee, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61779 exists.\n\nAffected product: confidential-containers trustee. 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-2025-61779/ (Markdown: https://insights.sbomify.com/CVE-2025-61779/index.md)","id":"CVE-2025-61779","markdown":"https://insights.sbomify.com/CVE-2025-61779/index.md","name":"CVE-2025-61779","record":{"aliases":["GHSA-49mc-2q77-m99x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Confidential Containers Trustee","requires_auth":"none","summary":"Unauthenticated attackers can modify attestation policies in Trustee, potentially bypassing security controls for confidential containers.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Confidential Containers's Trustee project contains tools and components for attesting confidential guests and providing secrets to them. In versions prior to 0.15.0, the attestation-policy endpoint didn't check if the kbs-client submitting the request was actually authenticated (had the right key). This allowed any kbs-client to actually change the attestation policy. Version 0.15.0 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Trustee's attestation-policy endpoint is not protected by admin autentication","id":"CVE-2025-61779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Rack has Possible Information Disclosure Vulnerability","id":"CVE-2025-61780"},"packages":[],"prev":{"headline":"Akka.Remote TLS did not properly implement certificate-based authentication","id":"CVE-2025-61778"},"products":["trustee"],"published":"2025-10-09","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-10","vendors":["confidential-containers"]},"summary":"Unauthenticated attackers can modify attestation policies in Trustee, potentially bypassing security controls for confidential containers.","url":"https://insights.sbomify.com/CVE-2025-61779/"}