{"answers":{"affected":"2 open source packages ship an affected version, including stigmem-node.","exploited":"There is no known exploitation of CVE-2026-76245 in the wild and no public exploit code.","fix":"Upgrade stigmem-node to 0.9.0a2 or later.","what":"CVE-2026-76245 is a high-severity authentication bypass vulnerability in eidetic-labs stigmem, 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-76245 and fix it if it is affected.\n\nWhat it is: CVE-2026-76245 is a high-severity authentication bypass vulnerability in eidetic-labs stigmem, 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-76245 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-76245/ (Markdown: https://insights.sbomify.com/CVE-2026-76245/index.md)","id":"CVE-2026-76245","markdown":"https://insights.sbomify.com/CVE-2026-76245/index.md","name":"CVE-2026-76245","record":{"aliases":["GHSA-rh24-296r-8rj6","GHSA-xh5j-xjfq-qvvx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python federation library","requires_auth":"low_privilege","summary":"Attackers can cause denial of service in authenticated federation flows by exploiting timestamp validation flaws in the stigmem library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"stigmem (pip package stigmem-node) version 0.9.0a1 contains a timestamp-handling mismatch in federation peer-token validation that can cause valid peer tokens to be incorrectly treated as expired. This affects the availability and reliability of authenticated federation flows on nodes using federation peer authentication paths. The issue is fixed in 0.9.0a2, which uses the canonical millisecond-based validation path.","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 Token Timestamp Validation Bypass","id":"CVE-2026-76245","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":"Missing Authorization through REST API Endpoints in the Splunk App for Splunk Observability Cloud","id":"CVE-2026-76251"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":null,"source":"GHSA-xh5j-xjfq-qvvx"},{"ecosystem":"PyPI","fixed":["0.9.0a2"],"introduced":["0"],"last_affected":[],"package":"stigmem-node","purl":"pkg:pypi/stigmem-node","source":"GHSA-xh5j-xjfq-qvvx"}],"prev":{"headline":"stigmem-node Insecure Federation Transport Configuration","id":"CVE-2026-76244"},"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":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["eidetic-labs"]},"summary":"Attackers can cause denial of service in authenticated federation flows by exploiting timestamp validation flaws in the stigmem library.","url":"https://insights.sbomify.com/CVE-2026-76245/"}