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.
CVE-2026-76240
HIGHPre-NVD 7.57.5—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Patch available. Sources: github.
generic
stigmem Postgres SQL Injection via Schema Identifier | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-postgres-sql-injection-via-schema-identifiergithub Patch Available
Postgres schema identifier handling required defensive quoting · Advisory · eidetic-labs/stigmem · GitHub
Affected: 0.9.0a2. Schema identifier handling now uses defensive identifier quoting and val
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-9pc9-4crj-mhpjVendor Advisories for CVE-2026-76240(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| stigmem-node | 0.9.0a1 | 0.9.0a2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 04:14 UTCEG score recompute
- 2026-08-21 04:14 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:38 UTCEG score recompute
- 2026-08-20 16:38 UTCGHSA enrichment
- 2026-08-20 15:45 UTCEG score recompute
- 2026-08-20 15:45 UTCGHSA enrichment
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-20 02:02 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:12 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-76240?
CVE-2026-76240 is a high vulnerability published on August 19, 2026. 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.…
When was CVE-2026-76240 disclosed?
CVE-2026-76240 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76240 actively exploited?
CVE-2026-76240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-76240?
CVE-2026-76240 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-76240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76240, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76240
Is Your Infrastructure Affected by CVE-2026-76240?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.