CVE-2026-76244

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-62408 (ENISA EUVD) · GHSA-pxm8-2h3h-jwmv (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

stigmem-node contains an insecure default configuration vulnerability that allows federation traffic to traverse networks without mTLS protection when non-loopback endpoints are enabled. Operators who explicitly disabled mTLS while binding federation to non-loopback addresses expose federation traffic to cleartext interception and man-in-the-middle attacks.

CVSS
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
Web page

stigmem-node Insecure Federation Transport Configuration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/stigmem-node-insecure-federation-transport-configuration
GitHub advisoryMentions a patch (unverified)

Federation insecure transport settings may allow non-loopback cleartext federation · Advisory · eidetic-labs/stigmem · GitHub

Affected: 0.9.0a2. The node now refuses this configuration unless insecure federation is li

https://github.com/eidetic-labs/stigmem/security/advisories/GHSA-jmfc-hfjq-pxcp

Vendor Advisories for CVE-2026-76244(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)
PackageVulnerable rangeFix by version rangeDependents
stigmem-node0.9.0a1
  • every version up to 0.9.0a2: fixed in 0.9.0a2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 62× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 448 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 348 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 17:02 UTCEchelonGraph re-scored
  2. 2026-11-12 17:02 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-11-11 18:33 UTCEchelonGraph re-scored
  5. 2026-11-11 18:33 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-11-10 20:03 UTCEchelonGraph re-scored
  8. 2026-11-10 20:03 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-11-09 21:34 UTCEchelonGraph re-scored
  11. 2026-11-09 21:34 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  12. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-11-08 23:06 UTCEchelonGraph re-scored
  14. 2026-11-08 23:06 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-11-08 00:37 UTCEchelonGraph re-scored
  17. 2026-11-08 00:37 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-11-07 02:09 UTCEchelonGraph re-scored
  20. 2026-11-07 02:09 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  21. 2026-11-06 17:55 UTCOSV refresh
  22. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-11-06 03:40 UTCEchelonGraph re-scored
  24. 2026-11-06 03:40 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 75 more
  1. 2026-11-05 05:12 UTCEchelonGraph re-scored
  2. 2026-11-05 05:12 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-11-04 06:43 UTCEchelonGraph re-scored
  5. 2026-11-04 06:43 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  6. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-11-03 08:14 UTCEchelonGraph re-scored
  8. 2026-11-03 08:14 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  9. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-11-02 09:46 UTCEchelonGraph re-scored
  11. 2026-11-02 09:46 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-11-01 11:17 UTCEchelonGraph re-scored
  14. 2026-11-01 11:17 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-31 12:48 UTCEchelonGraph re-scored
  17. 2026-10-31 12:48 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  18. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-30 14:19 UTCEchelonGraph re-scored
  20. 2026-10-30 14:19 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  21. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-29 15:51 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  23. 2026-10-28 17:22 UTCEchelonGraph re-scored
  24. 2026-10-28 17:22 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  25. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-10-27 18:50 UTCEchelonGraph re-scored
  27. 2026-10-27 18:50 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  28. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-10-26 20:22 UTCEchelonGraph re-scored
  30. 2026-10-26 20:21 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  31. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-10-25 20:05 UTCEchelonGraph re-scored
  33. 2026-10-25 20:05 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  34. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-10-25 14:02 UTCEchelonGraph re-scored
  36. 2026-10-24 21:36 UTCEchelonGraph re-scored
  37. 2026-10-24 21:36 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  38. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-10-23 23:08 UTCEchelonGraph re-scored
  40. 2026-10-23 23:08 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  41. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-10-23 00:26 UTCEchelonGraph re-scored
  43. 2026-10-23 00:26 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  44. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-10-22 01:34 UTCEchelonGraph re-scored
  46. 2026-10-22 01:34 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  47. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-10-21 03:06 UTCEchelonGraph re-scored
  49. 2026-10-21 03:05 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  50. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-10-20 04:28 UTCEchelonGraph re-scored
  52. 2026-10-20 04:28 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  53. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-10-19 05:18 UTCEchelonGraph re-scored
  55. 2026-10-19 05:18 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  56. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-10-18 06:48 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  58. 2026-10-18 03:13 UTCEchelonGraph re-scored
  59. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-10-17 06:06 UTCEchelonGraph re-scored
  61. 2026-10-17 06:06 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  62. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-10-16 07:13 UTCEchelonGraph re-scored
  64. 2026-10-16 07:13 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  65. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-10-15 06:03 UTCEchelonGraph re-scored
  67. 2026-10-15 06:02 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  68. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-10-14 01:41 UTCEchelonGraph re-scored
  70. 2026-10-14 01:41 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  71. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-10-12 21:52 UTCEchelonGraph re-scored
  73. 2026-10-12 21:51 UTCGHSA enrichmentGHSA-pxm8-2h3h-jwmv · GitHub severity CRITICAL
  74. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  75. 2026-10-12 15:38 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-76244?
CVE-2026-76244 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. stigmem-node contains an insecure default configuration vulnerability that allows federation traffic to traverse networks without mTLS protection when non-loopback endpoints are enabled. Operators who explicitly disabled mTLS while binding federation to non-loopback addresses expose federation…
When was CVE-2026-76244 made public?
CVE-2026-76244 was made public on May 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-76244 actively exploited?
CVE-2026-76244 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76244?
CVE-2026-76244 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76244?
A fix for CVE-2026-76244 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76244 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76244

Explore →

Is Your Infrastructure Affected by CVE-2026-76244?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.