CVE-2026-31839 — @striae-org/striae
HIGHCVE-2026-31839 is a high-severity (CVSS 8.2) CWE-354 vulnerability in @striae-org/striae. A fix is available for @striae-org/striae — see the affected versions and patch details below.
Striae has a hash validation utility vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-31839.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-31839 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@striae-org/striaenpmDescription
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.0or 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @striae-org/striae | ≥ 0.9.22-0&&< 3.0.0 | 3.0.0npm install @striae-org/striae@3.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @striae-org/striae, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @striae-org/striae to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-31839 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-31839 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-31839. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-31839 in your dependencies?
O3 Security finds CVE-2026-31839 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.