{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76239 exists.","fix":"Upgrade stigmem-node to 0.9.0a11 or later.","what":"CVE-2026-76239 is a medium-severity server-side request forgery 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-76239 and fix it if it is affected.\n\nWhat it is: CVE-2026-76239 is a medium-severity server-side request forgery 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76239 exists.\n\nAffected packages and fixed versions:\n- stigmem-node (PyPI): affected all versions; fixed in 0.9.0a11\n- stigmem-node (PyPI): affected all versions; fixed in 0.9.0a11\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-76239/ (Markdown: https://insights.sbomify.com/CVE-2026-76239/index.md)","id":"CVE-2026-76239","markdown":"https://insights.sbomify.com/CVE-2026-76239/index.md","name":"CVE-2026-76239","record":{"aliases":["GHSA-5p3m-vhh6-9236","GHSA-xq22-gq5h-mvx5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Stigmem server","requires_auth":"low_privilege","summary":"Authenticated users can trigger server-side requests to internal services via unvalidated webhook addresses, enabling blind SSRF attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Stigmem before 0.9.0a11 fails to validate the delivery_address parameter when creating webhook subscriptions, allowing authenticated users to specify internal loopback and private network destinations. Attackers can trigger matching fact-change events to cause the Stigmem server to issue server-side HTTP POST requests to internal services, enabling blind SSRF attacks against localhost and private network endpoints.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Stigmem before 0.9.0a11 SSRF via unvalidated webhook delivery_address","id":"CVE-2026-76239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"stigmem Postgres SQL Injection via Schema Identifier","id":"CVE-2026-76240"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a11"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-5p3m-vhh6-9236"},{"ecosystem":"PyPI","fixed":["0.9.0a11"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-5p3m-vhh6-9236"}],"prev":{"headline":"stigmem before 0.9.0a12 Cross-Tenant BOLA via decay sweep","id":"CVE-2026-76238"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["eidetic-labs"]},"summary":"Authenticated users can trigger server-side requests to internal services via unvalidated webhook addresses, enabling blind SSRF attacks.","url":"https://insights.sbomify.com/CVE-2026-76239/"}