EUVD-2026-62405
GHSA-q84h-wr78-498w
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local vector with high complexity (AC:H) because two operator-introduced preconditions must co-occur; low privileges needed once conditions exist; no scope change beyond the process.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Arbitrary code execution is possible in stigmem-node versions before 0.9.0a2 when a single configuration flag is used to disable plugin signature enforcement without a required second acknowledgment. Operators who carry this permissive setting from development into shared or production environments create a condition where any user with write access to the plugin directory can inject and execute unsigned, potentially malicious plugin code with the process's privileges. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires two concurrent preconditions to be satisfied: first, an operator must have set the configuration flag that disables plugin signature enforcement - this is a non-default operator action, as the advisory implies enforcement is enabled by default; second, the plugin directory must be writable by users with lower trust than the process owner. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 7.3 with AV:L, PR:L, and AT:P reflects a nuanced risk profile: while the impact is high (full VC:H/VI:H/VA:H), exploitation is gated by two operator-introduced preconditions that would not exist in a correctly configured production deployment. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A developer sets the single disable-signature-enforcement flag during local testing and inadvertently promotes this configuration to a shared staging environment where the plugin directory is writable by other team members or service accounts. A less-trusted local user with write access to the plugin directory places an unsigned malicious plugin file in that directory; stigmem-node loads and executes it during its next plugin initialization cycle, granting the attacker arbitrary code execution under the process owner's privileges. … |
| Remediation | Upgrade stigmem-node to version 0.9.0a2 or later using 'pip install --upgrade --pre stigmem-node'; if using the Stigmem meta-package, use 'pip install --upgrade --pre stigmem[node]'. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all stigmem-node deployments and audit configuration files for disabled plugin signature enforcement flags; disable any such settings immediately in production environments. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Anonymous read/write/federation access to Stigmem nodes (versions before 0.9.0a2) is possible when operators disable aut
Federation peer-registration authentication bypass in stigmem-node 0.9.0a1 lets a network-positioned attacker enroll a r
Cleartext exposure of federation traffic in eidetic-labs stigmem-node (versions before 0.9.0a2) occurs when operators ex
Cross-tenant broken object level authorization (BOLA) in stigmem-node exposes quarantined facts across tenant boundaries
SQL injection in stigmem-node 0.9.0a1 stems from PostgreSQL schema identifiers being interpolated into SQL strings witho
Cross-tenant broken object level authorization (BOLA) in stigmem-node's decay sweep endpoint allows any authenticated wr
Cross-tenant broken object level authorization in stigmem-node before 0.9.0a12 allows an authenticated tenant in a multi
Availability disruption in stigmem-node 0.9.0a1 (pip package by eidetic-labs) allows authenticated federation peers to h
Blind Server-Side Request Forgery in Stigmem before 0.9.0a11 allows authenticated users to redirect the application serv
Same weakness CWE-494 – Download of Code Without Integrity Check
View allShare
External POC / Exploit Code
Leaving vuln.today