CVE-2026-31839

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.

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

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.

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

CVE-2026-31839 has a CVSS score of 8.2 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-31839? CVE-2026-31839 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in @striae-org/striae (npm), affecting versions >= 0.9.22-0, < 3.0.0. It is fixed in 3.0.0. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
2. How severe is CVE-2026-31839? CVE-2026-31839 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @striae-org/striae are affected by CVE-2026-31839? @striae-org/striae (npm) versions >= 0.9.22-0, < 3.0.0 is affected.
4. Is there a fix for CVE-2026-31839? Yes. CVE-2026-31839 is fixed in 3.0.0. Upgrade to this version or later.
5. Is CVE-2026-31839 exploitable, and should I be worried? Whether CVE-2026-31839 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-31839 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-31839? Upgrade @striae-org/striae to 3.0.0 or later.