Advisory record · GHSA-9pc9-4crj-mhpj

stigmem-node's Postgres schema identifier handling required defensive quoting

CVSS 7.5 HighEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 29 May 2026, 22:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stigmem-nodePyPI<0.9.0a20.9.0a2
Identifiers
GHSA-9pc9-4crj-mhpj · CVE-2026-76240
Weakness (CWE)
CWE-89
Published
29 May 2026
Updated
20 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

stigmem-node versions before 0.9.0a2 interpolated Postgres schema identifiers into SQL strings. The source says the schema value is operator-controlled in the reviewed code path, so exploitation is not described as currently reachable; the source states the pattern would be unsafe if future code let tenant or request input set schema names. Upgrade to stigmem-node 0.9.0a2, which adds identifier quoting and validation. Until then, set Postgres schema names only from trusted deployment configuration.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.