Striae has a hash validation utility vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-31839: 0.13% estimated exploitation activity in the next 30 days; percentile 2.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact Confirmation package integrity could be bypassed because both content and hash values were mutable in the same trust boundary. An attacker with access to an exported package could alter confirmation data and recompute hashes so hash-only checks still passed. This affects users relying on digital confirmations as an immutability and forensic chain-of-custody control. Patches Patched in v3.0.0. Upgrade to: - v3.0.0 or later Security behavior added in v3.0.0: - Server-issued asymmetric signatures for forensic manifests - Canonical payload signature verification during import and manual hash verification - Fail-closed behavior when signature metadata is missing or invalid - Signature/key…

Published by the source

11 Mar 2026, 14:55 UTC

Last modified by the source

13 Mar 2026, 10:56 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mmf8-487q-p45m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mmf8-487q-p45m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31839

Advisory: Striae has a hash validation utility vulnerability
IDs: CVE-2026-31839, GHSA-mmf8-487q-p45m
Record: https://patchnext.com/advisories/cve-2026-31839 (revision 2, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @striae-org/striae 3.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @striae-org/striae: affected >= 0.9.22-0, < 3.0.0; fixed in 3.0.0

## Suggested inspection (read-only)
- `npm ls @striae-org/striae --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @striae-org/striae.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mmf8-487q-p45m (OSV record GHSA-mmf8-487q-p45m lists affected ranges: npm @striae-org/striae >=0.9.22-0 <3.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-mmf8-487q-p45m (GitHub-reviewed advisory GHSA-mmf8-487q-p45m lists affected ranges: npm @striae-org/striae >=0.9.22-0 <3.0.0)

Commands are suggestions: review each one before running it.