{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"There is no known exploitation of CVE-2026-76241 in the wild and no public exploit code.","fix":"Upgrade stigmem-node to 0.9.0a2 or later.","what":"CVE-2026-76241 is a high-severity vulnerability in eidetic-labs stigmem, published on 19 Aug 2026. 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-2026-76241 and fix it if it is affected.\n\nWhat it is: CVE-2026-76241 is a high-severity vulnerability in eidetic-labs stigmem, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76241 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-76241/ (Markdown: https://insights.sbomify.com/CVE-2026-76241/index.md)","id":"CVE-2026-76241","markdown":"https://insights.sbomify.com/CVE-2026-76241/index.md","name":"CVE-2026-76241","record":{"aliases":["GHSA-q84h-wr78-498w","GHSA-w7pm-9g55-mxfm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Node.js plugin library","requires_auth":"low_privilege","summary":"Attackers can bypass plugin signature enforcement via configuration to execute arbitrary code if plugin directories are writable.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsigned (potentially malicious) plugin code could be loaded and executed, resulting in arbitrary code execution. Fixed in 0.9.0a2, which requires a second explicit acknowledgment to disable signature enforcement.","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 Plugin Signature Enforcement Bypass via Configuration","id":"CVE-2026-76241","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"stigmem Federation Peer Registration Authentication Bypass","id":"CVE-2026-76242"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-w7pm-9g55-mxfm"},{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-w7pm-9g55-mxfm"}],"prev":{"headline":"stigmem Postgres SQL Injection via Schema Identifier","id":"CVE-2026-76240"},"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-21","vendors":["eidetic-labs"]},"summary":"Attackers can bypass plugin signature enforcement via configuration to execute arbitrary code if plugin directories are writable.","url":"https://insights.sbomify.com/CVE-2026-76241/"}