{"answers":{"affected":"2 open source packages ship an affected version, including @striae-org/striae. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31839 in the wild and no public exploit code.","fix":"Upgrade @striae-org/striae to 3.0.0 or later.","what":"CVE-2026-31839 is a high-severity vulnerability in striae-org striae, published on 11 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-31839 and fix it if it is affected.\n\nWhat it is: CVE-2026-31839 is a high-severity vulnerability in striae-org striae, published on 11 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-31839 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @striae-org/striae (npm): affected from 0.9.22-0; fixed in 3.0.0\n- @striae-org/striae (npm): affected from 0.9.22-0; fixed in 3.0.0\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-31839/ (Markdown: https://insights.sbomify.com/CVE-2026-31839/index.md)","id":"CVE-2026-31839","markdown":"https://insights.sbomify.com/CVE-2026-31839/index.md","name":"CVE-2026-31839","record":{"aliases":["GHSA-mmf8-487q-p45m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Firearms comparison software","requires_auth":"none","summary":"Attackers can bypass integrity checks in Striae by modifying manifest hashes alongside package content, allowing tampered confirmation packages to pass validation.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"striae","vendor":"striae"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"Striae is a firearms examiner's comparison companion. A high-severity integrity bypass vulnerability existed in Striae's digital confirmation workflow prior to v3.0.0. Hash-only validation trusted manifest hash fields that could be modified together with package content, allowing tampered confirmation packages to pass integrity checks. This vulnerability is fixed in 3.0.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Striae has a hash validation utility vulnerability","id":"CVE-2026-31839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Parse Server has a SQL injection via dot-notation field name in PostgreSQL","id":"CVE-2026-31840"},"packages":[{"ecosystem":"npm","fixed":["3.0.0"],"introduced":["0.9.22-0"],"last_affected":[],"package":"@striae-org/striae","purl":null,"source":"GHSA-mmf8-487q-p45m"},{"ecosystem":"npm","fixed":["3.0.0"],"introduced":["0.9.22-0"],"last_affected":[],"package":"@striae-org/striae","purl":"pkg:npm/%40striae-org/striae","source":"GHSA-mmf8-487q-p45m"}],"prev":{"headline":"Auth bypass in istio","id":"CVE-2026-31838"},"products":["striae"],"published":"2026-03-11","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":"US public information, NVD API terms","name":"NVD"},{"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-03-11","vendors":["striae-org"]},"summary":"Attackers can bypass integrity checks in Striae by modifying manifest hashes alongside package content, allowing tampered confirmation packages to pass validation.","url":"https://insights.sbomify.com/CVE-2026-31839/"}