highVulnerability

GHSA-9pc9-4crj-mhpj

### Impact Postgres backend schema identifiers were interpolated into SQL strings. In the reviewed code path the schema value is operator-controlled, but the pattern was unsafe if future call sites allowed tenant or request-controlled schema names. Impacted users are operators using the Postgres backend in affected versions. ### Patches Patched in 0.9.0a2. Schema identifier handling now uses defensive identifier quoting and validation-oriented regression coverage. ### Workarounds Before upgrading, only configure Postgres schema names from trusted deployment configuration and do not derive schema names from request, tenant, header, or user input. ### Upgrade Upgrade to the patched release: ```bash pip install --upgrade --pre stigmem-node ``` If developers install through the Stigmem meta-package instead, they should use the matching extra for deployments, for example: ```bash pip install --upgrade --pre 'stigmem[node]' ``` ### Resources - Release: https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2 - Changelog: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35 - Security policy and posture: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md

Properties

ghsa_id
GHSA-9pc9-4crj-mhpj
severity
high
summary
stigmem-node's Postgres schema identifier handling required defensive quoting
cve_id
GHSA-9pc9-4crj-mhpj
is_ghsa_only
true
ghsa_published
2026-05-29T22:15:40Z
source_url
https://github.com/advisories/GHSA-9pc9-4crj-mhpj
ghsa_updated
2026-05-29T22:15:41Z

Related Entities (4)

VULNERABLE_TO (1)

[Software]pip/stigmem-node

AFFECTS (1)

[Software]pip/stigmem-node

HAS_WEAKNESS (1)

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

REPORTED_BY (1)

[Source]GitHub Advisory Database

Explore deeper with Ninja Signal's threat intelligence graph

GHSA-9pc9-4crj-mhpj — Ninja Signal Threat Intelligence | Ninja Signal