CVE-2026-76244Network attack vector

Traffic interception via mTLS-disabled federation

Published Aug 19, 2026 · Updated Aug 19, 2026

Cleartext transmission in Eidetic Labs Stigmem before 0.9.0a2 allows attackers to intercept federation traffic via non-loopback deployments with mTLS disabled. The stigmem-node configuration gate accepts a federation bind on a non-loopback URL even when mutual TLS is turned off, so inter-node traffic is sent without the intended transport authentication or encryption. Exposure requires federation to be enabled and explicitly configured this way; loopback-only local development is the intended insecure case, while reachable peers can be subjected to sniffing or man-in-the-middle tampering.

CVSS severity9.1
Critical
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cleartext transmission in Eidetic Labs Stigmem before 0.9.0a2 allows attackers to intercept federation traffic via non-loopback deployments with mTLS disabled. The stigmem-node configuration gate accepts a federation bind on a non-loopback URL even when mutual TLS is turned off, so inter-node traffic is sent without the intended transport authentication or encryption. Exposure requires federation to be enabled and explicitly configured this way; loopback-only local development is the intended insecure case, while reachable peers can be subjected to sniffing or man-in-the-middle tampering.

The record

CVE
CVE-2026-76244
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Eidetic Labs
Product
Stigmem
Classifications
CWE-319, T1557
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <0.9.0a2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Eidetic Labs · Stigmemversion=0 <0.9.0a2

Published CVSS scores

9.1VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-319Cleartext Transmission of Sensitive Information
T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo