CVE-2026-76240: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in eidetic-labs stigmem
stigmem-node version 0.9.0a1 contains an SQL injection vulnerability due to improper neutralization of special elements in SQL commands. The vulnerability arises because Postgres schema identifiers are interpolated into SQL strings without proper quoting or validation, allowing operator-controlled schema names to potentially inject SQL. This issue is fixed in version 0.9.0a2 by adding identifier quoting and validation. As a workaround, schema names should only be configured from trusted deployment configurations.
AI Analysis
Technical Summary
CVE-2026-76240 describes an SQL injection vulnerability in stigmem-node 0.9.0a1 where Postgres backend schema identifiers are directly interpolated into SQL strings without defensive quoting. The schema value is operator-controlled, which could lead to SQL injection if schema names are derived from tenant, request, or user input. The vulnerability is fixed in version 0.9.0a2 by implementing identifier quoting and validation to prevent injection. Until upgrading, it is recommended to only use trusted schema names from deployment configuration.
Potential Impact
An attacker with the ability to influence the schema identifier value could exploit this vulnerability to perform SQL injection attacks, potentially compromising the database integrity and confidentiality. The CVSS 4.0 score of 7.5 reflects a high severity with network attack vector, low attack complexity, and partial privileges required. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade stigmem-node to version 0.9.0a2 or later, which includes proper identifier quoting and validation to prevent SQL injection. As a temporary workaround, ensure schema names are configured only from trusted deployment configurations and not from user-controllable input.
CVE-2026-76240: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in eidetic-labs stigmem
Description
stigmem-node version 0.9.0a1 contains an SQL injection vulnerability due to improper neutralization of special elements in SQL commands. The vulnerability arises because Postgres schema identifiers are interpolated into SQL strings without proper quoting or validation, allowing operator-controlled schema names to potentially inject SQL. This issue is fixed in version 0.9.0a2 by adding identifier quoting and validation. As a workaround, schema names should only be configured from trusted deployment configurations.
CVSS v4.0
Score 7.5high
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-76240 describes an SQL injection vulnerability in stigmem-node 0.9.0a1 where Postgres backend schema identifiers are directly interpolated into SQL strings without defensive quoting. The schema value is operator-controlled, which could lead to SQL injection if schema names are derived from tenant, request, or user input. The vulnerability is fixed in version 0.9.0a2 by implementing identifier quoting and validation to prevent injection. Until upgrading, it is recommended to only use trusted schema names from deployment configuration.
Potential Impact
An attacker with the ability to influence the schema identifier value could exploit this vulnerability to perform SQL injection attacks, potentially compromising the database integrity and confidentiality. The CVSS 4.0 score of 7.5 reflects a high severity with network attack vector, low attack complexity, and partial privileges required. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade stigmem-node to version 0.9.0a2 or later, which includes proper identifier quoting and validation to prevent SQL injection. As a temporary workaround, ensure schema names are configured only from trusted deployment configurations and not from user-controllable input.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-19T11:38:33.224Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85bc80acd9273b492f4a32
Added to database: 08/19/2026, 14:24:00 UTC
Last enriched: 08/19/2026, 14:37:50 UTC
Last updated: 08/20/2026, 00:37:27 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.