CVE-2026-76240
Received Received - Intake

SQL Injection in stigmem-node

Vulnerability report for CVE-2026-76240, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-19

Last updated on: 2026-08-19

Assigner: VulnCheck

Description

stigmem-node 0.9.0a1 interpolates Postgres backend schema identifiers into SQL strings without defensive quoting. In the affected code path the schema value is operator-controlled, but the unsafe pattern could allow SQL injection if a schema name were derived from tenant, request, or user input. Fixed in 0.9.0a2, which adds identifier quoting and validation. As a workaround, only configure schema names from trusted deployment configuration.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-19
Last Modified
2026-08-19
Generated
2026-08-19
AI Q&A
2026-08-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
stigmem stigmem-node to 0.9.0a2 (exc)
eidetic_labs stigmem_node to 0.9.0a2 (exc)
eidetic_labs stigmem_node From 0.9.0a1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-76240 is a SQL injection vulnerability in stigmem-node 0.9.0a1 where Postgres backend schema identifiers are directly interpolated into SQL strings without proper quoting or validation. This allows attackers to manipulate SQL queries if schema names come from untrusted sources like tenant or user input.

Detection Guidance

To detect this vulnerability, check if your system is running stigmem-node version 0.9.0a1 or earlier. Use commands like 'pip show stigmem-node' or 'npm list stigmem-node' to verify the installed version. If the version is below 0.9.0a2, the system is vulnerable.

Impact Analysis

This vulnerability could allow attackers with high privileges to execute unauthorized SQL commands, potentially leading to data theft, modification, or deletion. It may also enable attackers to bypass security controls or gain full control over the database.

Compliance Impact

This vulnerability could lead to violations of GDPR (data protection) and HIPAA (health data security) by enabling unauthorized access to sensitive data. Compliance failures may result in legal penalties, fines, or reputational damage.

Mitigation Strategies

Immediately upgrade stigmem-node to version 0.9.0a2 or later. If upgrading is not possible, configure schema names only from trusted deployment configurations to prevent SQL injection via untrusted inputs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76240. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart