Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@striae-org/striae

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.2npmAmendedPublished

    Striae has a hash validation utility vulnerability

    CVE-2026-31839 · GHSA-mmf8-487q-p45m

    Affected
    • npm @striae-org/striae >= 0.9.22-0, < 3.0.0
    Fixed in
    3.0.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 3.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →