Skip to main content
EPSS 0.1%top 99%

CVE-2026-76241: Download of Code Without Integrity Check in eidetic-labs stigmem

0
High
Published: 08/19/2026 (08/19/2026, 14:02:18 UTC)
Source: CVE Database V5
Vendor/Project: eidetic-labs
Product: stigmem

Description

stigmem-node versions before 0.9.0a2 allow disabling plugin signature enforcement with a single configuration flag, which can lead to loading and executing unsigned plugin code if plugin directories are writable by less-trusted users. This vulnerability enables arbitrary code execution. The issue is fixed in version 0.9.0a2 by requiring a second explicit acknowledgment to disable signature enforcement.

CVSS v4.0

Score 7.3high

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

eidetic-labs

stigmem

Affected versions
>=0 <0.9.0a2
GitHub Actionsmore threats →ai
eidetic-labs/stigmem
pkg:github/eidetic-labs/stigmem
Affected versions
=0.9.0

Run 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

AILast updated: 09/11/2026, 08:33:06 UTC

Technical Analysis

CVE-2026-76241 affects stigmem-node 0.9.0a1 and earlier versions, allowing an attacker to disable plugin signature enforcement via a single configuration flag without a second explicit confirmation. If the environment permits less-trusted users to write to plugin directories, unsigned and potentially malicious plugins can be loaded and executed, resulting in arbitrary code execution. The vulnerability is addressed in version 0.9.0a2, which introduces a requirement for a second explicit acknowledgment to disable signature enforcement.

Potential Impact

An attacker with the ability to write to plugin directories in affected stigmem-node environments can load and execute arbitrary unsigned plugin code, leading to arbitrary code execution with the privileges of the stigmem-node process. This can compromise the affected system's integrity and security.

Mitigation Recommendations

Upgrade stigmem-node to version 0.9.0a2 or later, which requires a second explicit acknowledgment to disable plugin signature enforcement, preventing accidental or unauthorized disabling of this security feature. Until upgraded, ensure that plugin directories are not writable by less-trusted users to mitigate the risk of loading unsigned plugins.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-19T11:38:33.225Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a85bc80acd9273b492f4a34

Added to database: 08/19/2026, 14:24:00 UTC

Last enriched: 09/11/2026, 08:33:06 UTC

Last updated: 10/04/2026, 10:02:29 UTC

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses