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.
Published: 2026-08-19
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The stigmem-node package v0.9.0a1 contains a flaw where schema identifiers used in PostgreSQL queries are directly interpolated into SQL strings without proper quoting. This allows a malicious actor to inject arbitrary SQL when controlling the schema name through tenant, request, or user input. The consequence is unauthorized data access or manipulation and makes the database vulnerable to data exfiltration or modification.

Affected Systems

This issue affects the stigmem-node application from eidetic‑labs, specifically version 0.9.0a1. The fix is available in version 0.9.0a2, which introduces identifier quoting and validation. Earlier releases are unpatched and vulnerable.

Risk and Exploitability

The vulnerability scores a CVSS of 7.5, rating it high severity. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a remote user providing a crafted schema name through the application interface or configuration that influences the SQL statement. Successful exploitation would give the attacker the same privileges as the database user and could lead to data theft, modification, or possible remote code execution if additional injection paths exist.

Generated by OpenCVE AI on August 19, 2026 at 18:56 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade stigmem-node to version 0.9.0a2 or newer, which applies proper quoting and validation.
  • If upgrade cannot be performed immediately, limit the schema names to values set in trusted deployment configuration and avoid using user-supplied input for schema identifiers.
  • Conduct a code audit of all dynamic query constructions to ensure identifier values are safely quoted and validated, preventing similar injection opportunities.

Generated by OpenCVE AI on August 19, 2026 at 18:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
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.
Title stigmem Postgres SQL Injection via Schema Identifier
Weaknesses CWE-89
References
Metrics cvssV4_0

{'score': 7.5, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-19T14:02:18.061Z

Reserved: 2026-08-19T11:38:33.224Z

Link: CVE-2026-76240

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-19T14:17:56.300

Modified: 2026-08-19T14:17:56.300

Link: CVE-2026-76240

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-19T19:00:05Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')