CVE-2026-31839: @striae org/striae Striae Has A Hash Validation Vulnerability
HIGHCVE-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.
CVE-2026-31839 at a Glance
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).
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.
npm install @striae-org/striae@3.0.0Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @striae-org/striaeHow 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/striaeAnalyze 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
CVE-2026-31839 Affected @striae org/striae Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@striae-org/striae
|
npm |
≥ 0.9.22-0
< 3.0.0
|
3.0.0
|
References
Frequently Asked Questions
What is CVE-2026-31839?
Which @striae org/striae versions are affected?
What version fixes CVE-2026-31839?
Is @striae-org/striae affected?
What is the CVSS score of CVE-2026-31839?
What CWE is associated with CVE-2026-31839?
How can I check npm dependencies for CVE-2026-31839?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"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"
}
}