{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"There is no known exploitation of CVE-2026-76238 in the wild and no public exploit code.","fix":"Upgrade stigmem-node to 0.9.0a12 or later.","what":"CVE-2026-76238 is a high-severity missing authorization vulnerability in eidetic-labs stigmem-node, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76238 and fix it if it is affected.\n\nWhat it is: CVE-2026-76238 is a high-severity missing authorization vulnerability in eidetic-labs stigmem-node, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76238 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.0a12\n- stigmem-node (PyPI): affected all versions; fixed in 0.9.0a12\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-76238/ (Markdown: https://insights.sbomify.com/CVE-2026-76238/index.md)","id":"CVE-2026-76238","markdown":"https://insights.sbomify.com/CVE-2026-76238/index.md","name":"CVE-2026-76238","record":{"aliases":["GHSA-6gqw-jqv7-v88m","GHSA-w3ff-rjv9-m452"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js memory library","requires_auth":"low_privilege","summary":"Authenticated attackers can manipulate or view data across all tenants via the decay sweep endpoint in stigmem.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"stigmem versions before 0.9.0a12 contain a broken object level authorization vulnerability in the decay sweep endpoint that allows authenticated attackers with write credentials for one tenant to execute decay operations affecting all tenants. Attackers can submit POST requests to the decay sweep endpoint with ttl_seconds=0 to expire facts across all tenants, or use dry_run to obtain cross-tenant fact counts and existence information.","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 before 0.9.0a12 Cross-Tenant BOLA via decay sweep","id":"CVE-2026-76238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Stigmem before 0.9.0a11 SSRF via unvalidated webhook delivery_address","id":"CVE-2026-76239"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a12"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-6gqw-jqv7-v88m"},{"ecosystem":"PyPI","fixed":["0.9.0a12"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-6gqw-jqv7-v88m"}],"prev":{"headline":"stigmem before 0.9.0a12 Cross-Tenant BOLA via quarantine","id":"CVE-2026-76237"},"products":["stigmem-node"],"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-25","vendors":["eidetic-labs"]},"summary":"Authenticated attackers can manipulate or view data across all tenants via the decay sweep endpoint in stigmem.","url":"https://insights.sbomify.com/CVE-2026-76238/"}