Stigmem before 0.9.0a11 fails to validate the delivery_address parameter when creating webhook subscriptions, allowing authenticated users to specify internal loopback and private network destinations. Attackers can trigger matching fact-change events to cause the Stigmem server to issue server-side HTTP POST requests to internal services, enabling blind SSRF attacks against localhost and private network endpoints.
CVE-2026-76239
Score 6.3 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Stigmem before 0.9.0a11 SSRF via unvalidated webhook delivery_address | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stigmem-before-0a11-ssrf-via-unvalidated-webhook-delivery-addressBlind SSRF via unvalidated webhook subscription delivery_address · Advisory · eidetic-labs/stigmem · GitHub
https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-5p3m-vhh6-9236Vendor Advisories for CVE-2026-76239(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 8× in last 7d / 8× 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-20 22:56 UTCEPSS rescore
- 2026-08-20 14:00 UTCEG score recompute
- 2026-08-20 14:00 UTCGHSA enrichment
- 2026-08-19 15:24 UTCEG score recompute
- 2026-08-19 14:57 UTCEG score recompute
- 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)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-76239?
When was CVE-2026-76239 disclosed?
Is CVE-2026-76239 actively exploited?
What is the CVSS score of CVE-2026-76239?
How do I remediate CVE-2026-76239?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76239
Is Your Infrastructure Affected by CVE-2026-76239?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.