{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"There is no known exploitation of CVE-2026-76240 in the wild and no public exploit code.","fix":"Upgrade stigmem-node to 0.9.0a2 or later.","what":"CVE-2026-76240 is a high-severity SQL injection vulnerability in eidetic-labs stigmem, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76240 and fix it if it is affected.\n\nWhat it is: CVE-2026-76240 is a high-severity SQL injection vulnerability in eidetic-labs stigmem, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76240 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-76240/ (Markdown: https://insights.sbomify.com/CVE-2026-76240/index.md)","id":"CVE-2026-76240","markdown":"https://insights.sbomify.com/CVE-2026-76240/index.md","name":"CVE-2026-76240","record":{"aliases":["GHSA-9pc9-4crj-mhpj","GHSA-vgv8-r42h-hgr6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js Postgres library","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary SQL commands via unquoted schema identifiers in stigmem-node, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"stigmem-node 0.9.0a1 interpolates Postgres backend schema identifiers into SQL strings without defensive quoting. In the affected code path the schema value is operator-controlled, but the unsafe pattern could allow SQL injection if a schema name were derived from tenant, request, or user input. Fixed in 0.9.0a2, which adds identifier quoting and validation. As a workaround, only configure schema names from trusted deployment configuration.","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 Postgres SQL Injection via Schema Identifier","id":"CVE-2026-76240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"stigmem Plugin Signature Enforcement Bypass via Configuration","id":"CVE-2026-76241"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-9pc9-4crj-mhpj"},{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-9pc9-4crj-mhpj"}],"prev":{"headline":"Stigmem before 0.9.0a11 SSRF via unvalidated webhook delivery_address","id":"CVE-2026-76239"},"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 execute arbitrary SQL commands via unquoted schema identifiers in stigmem-node, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2026-76240/"}