{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53391 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-53391 is a critical vulnerability in Debian zulucrypt, published on 28 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53391 and fix it if it is affected.\n\nWhat it is: CVE-2025-53391 is a critical vulnerability in Debian zulucrypt, published on 28 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53391 exists.\n\nAffected product: Debian zulucrypt. 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-53391/ (Markdown: https://insights.sbomify.com/CVE-2025-53391/index.md)","id":"CVE-2025-53391","markdown":"https://insights.sbomify.com/CVE-2025-53391/index.md","name":"CVE-2025-53391","record":{"aliases":["DEBIAN-CVE-2025-53391","GHSA-33qm-768m-wx8p","UBUNTU-CVE-2025-53391","USN-8218-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux disk encryption tool","requires_auth":"none","summary":"Local attackers can escalate privileges to root due to insecure PolicyKit settings in zuluCrypt.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Debian zuluPolkit/CMakeLists.txt file for zuluCrypt through the zulucrypt_6.2.0-1 package has insecure PolicyKit allow_any/allow_inactive/allow_active settings that allow a local user to escalate their privileges to root.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Privilege escalation in zulucrypt","id":"CVE-2025-53391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in pfSense","id":"CVE-2025-53392"},"packages":[],"prev":{"headline":"Not used","id":"CVE-2025-53388"},"products":["zulucrypt"],"published":"2025-06-28","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-30","vendors":["Debian"]},"summary":"Local attackers can escalate privileges to root due to insecure PolicyKit settings in zuluCrypt.","url":"https://insights.sbomify.com/CVE-2025-53391/"}