{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"There is no known exploitation of CVE-2026-76242 in the wild and no public exploit code.","fix":"Upgrade stigmem-node to 0.9.0a2 or later.","what":"CVE-2026-76242 is a critical authentication bypass vulnerability in eidetic-labs stigmem, published on 19 Aug 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-76242 and fix it if it is affected.\n\nWhat it is: CVE-2026-76242 is a critical authentication bypass vulnerability in eidetic-labs stigmem, published on 19 Aug 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-76242 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stigmem-node (PyPI): affected all versions; fixed in 0.9.0a2\n- stigmem-node (PyPI): affected all versions; fixed in 0.9.0a2\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-76242/ (Markdown: https://insights.sbomify.com/CVE-2026-76242/index.md)","id":"CVE-2026-76242","markdown":"https://insights.sbomify.com/CVE-2026-76242/index.md","name":"CVE-2026-76242","record":{"aliases":["GHSA-9vp8-3hmv-8fgh","GHSA-rgmr-4wwg-2c6j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Federation node software","requires_auth":"none","summary":"Attackers can register malicious federation peers without administrator approval, allowing interception or tampering of federation traffic.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"stigmem-node 0.9.0a1 accepts federation peer key material during peer registration without a separate administrator out-of-band fingerprint approval step. On nodes that accept federation peer registration over a network where initial registration can be intercepted or misdirected, an attacker can register a malicious peer and gain access to or tamper with federation traffic. Fixed in 0.9.0a2, which introduces a pending approval flow requiring administrator fingerprint verification before peer tokens are accepted.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"stigmem Federation Peer Registration Authentication Bypass","id":"CVE-2026-76242","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"stigmem before 0.9.0a2 Authentication Bypass via Disabled Auth","id":"CVE-2026-76243"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-9vp8-3hmv-8fgh"},{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-9vp8-3hmv-8fgh"}],"prev":{"headline":"stigmem Plugin Signature Enforcement Bypass via Configuration","id":"CVE-2026-76241"},"products":["stigmem"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-08-20","vendors":["eidetic-labs"]},"summary":"Attackers can register malicious federation peers without administrator approval, allowing interception or tampering of federation traffic.","url":"https://insights.sbomify.com/CVE-2026-76242/"}