CVE-2026-76244
Default config allows federation traffic without mTLS, enabling MitM and interception.
Is CVE-2026-76244 being exploited?
Not confirmed. CVE-2026-76244 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-76244?
CVE-2026-76244 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76244?
Yes. A fix has been recorded for CVE-2026-76244. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76244 affect?
CVE-2026-76244 affects stigmem-node, deployments binding federation to non-loopback addresses. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76244?
Enable mTLS, avoid non-loopback federation binds, and apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Network attacker can intercept or perform MITM on federation traffic in cleartext when mTLS is disabled on non-loopback endpoints, exposing credentials and data.
Immediate action required
- affected< 0.9.0a2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.