stigmem versions before 0.9.0a2 allow unauthenticated access when authentication is disabled on non-loopback deployments. Attackers can perform read, write, and federation operations with anonymous identity when nodes are exposed outside local development environments.
CVE-2026-76243
This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.2
- EG Score
- 9.2(medium)
- EG Risk
- 46(Track)EG Risk 46/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 computedSeverity92% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026stigmem before 0.9.0a2 Authentication Bypass via Disabled Auth | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-before-0a2-authentication-bypass-via-disabled-authAuth-disabled deployments may grant broad anonymous access outside loopback · Advisory · eidetic-labs/stigmem · GitHub
Affected: 0.9.0a2. The node now refuses unauthenticated operation outside loopback-only loc
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-fp6w-8wpg-74g5Vendor Advisories for CVE-2026-76243(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× 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 06:36 UTCGHSA enrichment
- 2026-08-21 02:58 UTCGHSA enrichment
- 2026-08-20 23:19 UTCEG score recompute
- 2026-08-20 23:19 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 19:41 UTCGHSA enrichment
- 2026-08-20 16:03 UTCGHSA enrichment
- 2026-08-20 12:24 UTCGHSA enrichment
- 2026-08-20 08:46 UTCGHSA enrichment
- 2026-08-20 05:08 UTCGHSA enrichment
- 2026-08-20 01:30 UTCGHSA enrichment
- 2026-08-19 21:51 UTCGHSA enrichment
- 2026-08-19 18:12 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
Frequently asked(5)
What is CVE-2026-76243?
When was CVE-2026-76243 disclosed?
Is CVE-2026-76243 actively exploited?
What is the CVSS score of CVE-2026-76243?
How do I remediate CVE-2026-76243?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76243
Is Your Infrastructure Affected by CVE-2026-76243?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.