{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54871 exists.","fix":"No fix has been published for CVE-2025-54871 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54871 is a medium-severity vulnerability in steveseguin electroncapture, published on 5 Aug 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-54871 and fix it if it is affected.\n\nWhat it is: CVE-2025-54871 is a medium-severity vulnerability in steveseguin electroncapture, published on 5 Aug 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-54871 exists.\n\nAffected product: steveseguin electroncapture. 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-54871/ (Markdown: https://insights.sbomify.com/CVE-2025-54871/index.md)","id":"CVE-2025-54871","markdown":"https://insights.sbomify.com/CVE-2025-54871/index.md","name":"CVE-2025-54871","record":{"aliases":["GHSA-8849-p3j4-jq4h"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Electron Capture app","requires_auth":"low_privilege","summary":"Local attackers can bypass macOS TCC privacy protections to access sensitive files by exploiting misconfigured Node fuses in Electron Capture.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"electron_capture","vendor":"electroncapture"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Electron Capture facilitates video playback for screen-sharing and capture. In versions 2.19.1 and below, the elecap app on macOS allows local unprivileged users to bypass macOS TCC privacy protections by enabling ELECTRON_RUN_AS_NODE. This environment variable allows arbitrary Node.js code to be executed via the -e flag, which runs inside the main Electron context, inheriting any previously granted TCC entitlements (such as access to Documents, Downloads, etc.). This issue is fixed in version 2.20.0.","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":"Electron Capture is Vulnerable to TCC Bypass via Misconfigured Node Fuses (macOS)","id":"CVE-2025-54871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"onion-site-template tor Secrets Baked Into Image","id":"CVE-2025-54872"},"packages":[],"prev":{"headline":"VTun-ng's failure to initialize encryption modules may cause reversion to plaintext","id":"CVE-2025-54870"},"products":["electroncapture"],"published":"2025-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-08-05","vendors":["steveseguin"]},"summary":"Local attackers can bypass macOS TCC privacy protections to access sensitive files by exploiting misconfigured Node fuses in Electron Capture.","url":"https://insights.sbomify.com/CVE-2025-54871/"}