Description
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.
Published: 2026-08-19
Score: 9.1 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

stigmem‑node contains a default configuration that allows federation traffic to be sent across networks without mutual TLS when non‑loopback endpoints are enabled. This insecure transport exposes all federation packets to eavesdropping and tampering, permitting attackers to intercept, read, or modify messages. The weakness is classified as CWE‑319 – insecure communication, resulting in loss of confidentiality and integrity of data exchanged via federation services.

Affected Systems

The affected product is stigmem from eidetic‑labs. No specific version information is disclosed in the advisory; the issue applies to any instance where federation is bound to non‑loopback addresses and mutual TLS is explicitly disabled.

Risk and Exploitability

The vulnerability has a CVSS score of 9.1, indicating a critical condition. EPSS is not available and the flaw is not listed in the CISA KEV catalog. Attackers can exploit this by simply observing network traffic between nodes that have exposed non‑loopback federation endpoints without encryption. The exploit requires no special privileges and can be performed remotely over the network, resulting in a substantial risk for any environment that relies on stigmem federation for inter‑component communication.

Generated by OpenCVE AI on August 20, 2026 at 03:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Enable mutual TLS authentication for all federation traffic and enforce certificate verification on both ends
  • If mTLS cannot be applied immediately, restrict federation endpoints to loopback or internal interfaces and block external access to those ports
  • Apply any vendor‑supplied patches or updates that address the default configuration flaw as soon as available
  • Monitor logs and network traffic for unencrypted federation communication and investigate anomalies

Generated by OpenCVE AI on August 20, 2026 at 03:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
Description 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.
Title stigmem-node Insecure Federation Transport Configuration
Weaknesses CWE-319
References
Metrics cvssV4_0

{'score': 9.1, 'vector': '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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-19T14:30:02.087Z

Reserved: 2026-08-19T11:38:33.225Z

Link: CVE-2026-76244

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-19T14:17:56.827

Modified: 2026-08-19T15:18:11.240

Link: CVE-2026-76244

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T03:45:17Z

Weaknesses
  • CWE-319

    Cleartext Transmission of Sensitive Information