CVE-2026-76241: Download of Code Without Integrity Check in eidetic-labs stigmem
stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsigned (potentially malicious) plugin code could be loaded and executed, resulting in arbitrary code execution. Fixed in 0.9.0a2, which requires a second explicit acknowledgment to disable signature enforcement.
AI Analysis
Technical Summary
CVE-2026-76241 describes a vulnerability in stigmem-node 0.9.0 where plugin signature enforcement can be disabled with a single configuration flag. If this insecure configuration is used in an environment where plugin directories are writable by less-trusted users, attackers could place unsigned plugins that would be loaded and executed, resulting in arbitrary code execution. The vulnerability is resolved in version 0.9.0a2 by requiring a second explicit acknowledgment to disable signature enforcement, preventing accidental or unauthorized disabling of this security feature.
Potential Impact
An attacker with write access to plugin directories could introduce unsigned malicious plugins that the application would load and execute, leading to arbitrary code execution. This compromises the integrity and security of the affected system. The CVSS 4.0 score is 7.3 (high severity), reflecting the potential for privilege escalation and code execution with low attack complexity but requiring some privileges.
Mitigation Recommendations
Upgrade to stigmem-node version 0.9.0a2 or later, which enforces a second explicit acknowledgment before disabling plugin signature enforcement. This prevents accidental or unauthorized disabling of signature checks. Until upgraded, ensure that plugin directories are not writable by less-trusted users to reduce the risk of malicious plugin insertion. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in 0.9.0a2.
CVE-2026-76241: Download of Code Without Integrity Check in eidetic-labs stigmem
Description
stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsigned (potentially malicious) plugin code could be loaded and executed, resulting in arbitrary code execution. Fixed in 0.9.0a2, which requires a second explicit acknowledgment to disable signature enforcement.
CVSS v4.0
Score 7.3high
Affected software
pkg:github/eidetic-labs/stigmemRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76241 describes a vulnerability in stigmem-node 0.9.0 where plugin signature enforcement can be disabled with a single configuration flag. If this insecure configuration is used in an environment where plugin directories are writable by less-trusted users, attackers could place unsigned plugins that would be loaded and executed, resulting in arbitrary code execution. The vulnerability is resolved in version 0.9.0a2 by requiring a second explicit acknowledgment to disable signature enforcement, preventing accidental or unauthorized disabling of this security feature.
Potential Impact
An attacker with write access to plugin directories could introduce unsigned malicious plugins that the application would load and execute, leading to arbitrary code execution. This compromises the integrity and security of the affected system. The CVSS 4.0 score is 7.3 (high severity), reflecting the potential for privilege escalation and code execution with low attack complexity but requiring some privileges.
Mitigation Recommendations
Upgrade to stigmem-node version 0.9.0a2 or later, which enforces a second explicit acknowledgment before disabling plugin signature enforcement. This prevents accidental or unauthorized disabling of signature checks. Until upgraded, ensure that plugin directories are not writable by less-trusted users to reduce the risk of malicious plugin insertion. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in 0.9.0a2.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:38:33.225Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85bc80acd9273b492f4a34
Added to database: 08/19/2026, 14:24:00 UTC
Last enriched: 08/19/2026, 14:37:41 UTC
Last updated: 08/19/2026, 18:44:57 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.