Skip to content

Striae has a hash validation utility vulnerability

High severity GitHub Reviewed Published Mar 9, 2026 in striae-org/striae • Updated Mar 11, 2026

Package

npm @striae-org/striae (npm)

Affected versions

>= 0.9.22-0, < 3.0.0

Patched versions

3.0.0

Description

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 provenance support for audit-related workflows

Workarounds

There is no full cryptographic workaround equivalent to upgrading.

Temporary mitigations:

  • Treat hash-only validation as a tamper indicator, not proof of immutability
  • Restrict package exchange to trusted authenticated internal channels
  • Require out-of-band reviewer attestation for sensitive confirmation workflows
  • Pause imports from untrusted sources until upgraded

References

@StephenJLu StephenJLu published to striae-org/striae Mar 9, 2026
Published to the GitHub Advisory Database Mar 11, 2026
Reviewed Mar 11, 2026
Published by the National Vulnerability Database Mar 11, 2026
Last updated Mar 11, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(0th percentile)

Weaknesses

Use of a Broken or Risky Cryptographic Algorithm

The product uses a broken or risky cryptographic algorithm or protocol. Learn more on MITRE.

Missing Support for Integrity Check

The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum. Learn more on MITRE.

Improper Validation of Integrity Check Value

The product does not validate or incorrectly validates the integrity check values or checksums of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. Learn more on MITRE.

CVE ID

CVE-2026-31839

GHSA ID

GHSA-mmf8-487q-p45m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.