Vulnerabilities in pkg:npm/@striae-org/striae

PACKAGE
Advisory Identifier: GHSA-mmf8-487q-p45m
Share
Advisory Summary

CVE-2026-31839 is a HIGH (CVSS 8.2) striae has a hash validation vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting @striae org/striae libraries in the npm ecosystem. The issue involves striae has a hash validation utility vulnerability. Remediation is available by upgrading affected packages to version 3.0.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@striae-org/striae

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@striae-org/striae. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-mmf8-487q-p45m CVE-2026-31839 HIGH Striae has a hash validation utility vulnerability

CVE-2026-31839 at a Glance

CVE Identifier CVE-2026-31839
GHSA Identifier GHSA-mmf8-487q-p45m
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product @striae org/striae
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-31839

To remediate this vulnerability, upgrade all affected @striae org/striae dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@striae-org/striae fixed: 3.0.0 
npm install @striae-org/striae@3.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @striae-org/striae

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-31839, inspect your project dependencies using npm:

npm ls @striae-org/striae

Analyze the terminal output to locate any version of @striae org/striae in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.0), your application is affected.

Note: The npm ls @striae-org/striae command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In @striae org/striae, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-31839 Affected @striae org/striae Versions

1 component(s)
Fixed Versions:
3.0.0
Product / Package Ecosystem Affected Versions Fixed Version
@striae-org/striae
npm/@striae-org/striae
npm
≥ 0.9.22-0
< 3.0.0
3.0.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/striae-org/striae/security/advisories/GHSA-mmf8-487q-p45m
NVD — CVE-2026-31839 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-31839
@striae org/striae Source Repository REPOSITORY
https://github.com/striae-org/striae
@striae org/striae Release RELEASE
https://github.com/striae-org/striae/releases/tag/v3.0.0

Frequently Asked Questions

What is CVE-2026-31839?
CVE-2026-31839 is a security vulnerability in @striae org/striae involving Striae has a hash validation utility vulnerability under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which @striae org/striae versions are affected?
Affected versions include releases prior to 3.0.0 across affected packages: @striae-org/striae.
What version fixes CVE-2026-31839?
Upgrading to 3.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @striae-org/striae affected?
Yes, @striae-org/striae is affected in releases prior to 3.0.0. Upgrade your dependency to 3.0.0 or later.
What is the CVSS score of CVE-2026-31839?
CVE-2026-31839 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2026-31839?
CVE-2026-31839 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check npm dependencies for CVE-2026-31839?
Run the dependency tree command: 'npm ls @striae-org/striae'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mmf8-487q-p45m",
  "modified" : "2026-03-11T20:43:41Z",
  "published" : "2026-03-11T14:55:49Z",
  "aliases" : [ "CVE-2026-31839" ],
  "summary" : "Striae has a hash validation utility vulnerability",
  "details" : "## Summary\n\nA 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.\n\n## Impact\n\nConfirmation 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.\n\nThis affects users relying on digital confirmations as an immutability and forensic chain-of-custody control.\n\n## Patches\n\nPatched in **v3.0.0**.\n\nUpgrade to:\n- `v3.0.0` or later\n\nSecurity behavior added in v3.0.0:\n- Server-issued asymmetric signatures for forensic manifests\n- Canonical payload signature verification during import and manual hash verification\n- Fail-closed behavior when signature metadata is missing or invalid\n- Signature/key provenance support for audit-related workflows\n\n## Workarounds\n\nThere is no full cryptographic workaround equivalent to upgrading.\n\nTemporary mitigations:\n- Treat hash-only validation as a tamper indicator, not proof of immutability\n- Restrict package exchange to trusted authenticated internal channels\n- Require out-of-band reviewer attestation for sensitive confirmation workflows\n- Pause imports from untrusted sources until upgraded",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@striae-org/striae"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.9.22-0"
      }, {
        "fixed" : "3.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/striae-org/striae/security/advisories/GHSA-mmf8-487q-p45m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31839"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/striae-org/striae"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/striae-org/striae/releases/tag/v3.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327", "CWE-353", "CWE-354" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-11T14:55:49Z",
    "nvd_published_at" : "2026-03-11T17:16:58Z"
  }
}