stigmem-node
Affected
- introduced
0, fixed0.9.0a2(ecosystem)
Fixed versions
0.9.0a2
Fix
- Fixed version
0.9.0a2pip install --upgrade stigmem-node==0.9.0a2
Advisory
Also known as: CVE-2026-76240
stigmem-node's Postgres schema identifier handling required defensive quoting
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:
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:
pip install --upgrade --pre 'stigmem[node]'
Resources
High Basis: The source's own band: HIGH
0, fixed 0.9.0a2 (ecosystem)0.9.0a2
0.9.0a2pip install --upgrade stigmem-node==0.9.0a2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0