Skip to main content
EPSS 0.3%top 83%

CVE-2026-76244: Cleartext Transmission of Sensitive Information in eidetic-labs stigmem

0
Critical
Published: 08/19/2026 (08/19/2026, 14:02:20 UTC)
Source: CVE Database V5
Vendor/Project: eidetic-labs
Product: stigmem

Description

stigmem-node in eidetic-labs stigmem has a vulnerability where federation traffic can be transmitted without mTLS protection if non-loopback endpoints are enabled and mTLS is explicitly disabled. This insecure default configuration allows sensitive federation traffic to be exposed in cleartext, risking interception and man-in-the-middle attacks.

CVSS v4.0

Score 9.1critical

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Affected software

eidetic-labs

stigmem

Affected versions
>=0 <0.9.0a2

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 08:32:25 UTC

Technical Analysis

CVE-2026-76244 describes an insecure default configuration in eidetic-labs stigmem's stigmem-node component. When operators disable mutual TLS (mTLS) while binding federation services to non-loopback network addresses, federation traffic is transmitted without encryption. This cleartext transmission exposes the traffic to interception and man-in-the-middle attacks. The vulnerability affects versions from 0 up to but not including 0.9.0a2. The CVSS 4.0 score is 9.1, indicating a critical severity with network attack vector, low attack complexity, no privileges required, and high impact on confidentiality and integrity.

Potential Impact

Federation traffic can be intercepted or altered by attackers due to lack of mTLS encryption when non-loopback endpoints are used and mTLS is disabled. This compromises confidentiality and integrity of sensitive information transmitted between federated nodes.

Mitigation Recommendations

Operators should ensure mTLS is enabled when binding federation to non-loopback addresses to protect federation traffic. Upgrading to version 0.9.0a2 or later, where this issue is presumably fixed, is recommended. Patch status is not explicitly confirmed; check vendor advisories for updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-19T11:38:33.225Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a85bc80acd9273b492f4a3a

Added to database: 08/19/2026, 14:24:00 UTC

Last enriched: 09/11/2026, 08:32:25 UTC

Last updated: 10/04/2026, 10:02:29 UTC

Views: 72

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses