Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76242 – Federation Peer Registration Authentication Bypass – stigmem-node < 0.9.0a2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76242 is a critical authentication bypass vulnerability in stigmem-node (the stigmem-node PyPI package, part of the eidetic-labs stigmem project), affecting versions up to and including 0.9.0a1. The flaw stems from the federation peer registration process accepting peer key material without requiring an administrator to perform a separate, out-of-band fingerprint verification step. Given its network attack vector and high impact on confidentiality and integrity, this issue carries a severity score of 9.1 (Critical).

Technical details

  • Root cause: When a new federation peer registers with a stigmem-node instance, the node accepts the peer’s cryptographic key material immediately, without a mandatory administrator approval step that would independently verify the peer’s fingerprint out-of-band.
  • Trigger conditions: Exploitation requires the attacker to be positioned to intercept or influence the initial peer registration/key exchange (e.g., on a network path where registration traffic can be observed or redirected), and no user interaction is required.
  • Attack vector: Network (AV:N) — the flaw is reachable remotely via the federation peer registration mechanism; privileges required are none (PR:N).
  • Impact: A malicious actor can register a rogue peer as a trusted federation member, enabling interception and tampering with federation traffic between stigmem nodes — resulting in high confidentiality and high integrity impact on affected deployments.
  • Weakness classification: CWE-295 (Improper Certificate Validation) and CWE-345 (Insufficient Verification of Data Authenticity).

Affected software

  • Vendor/Project: eidetic-labs — stigmem
  • Package: stigmem-node (PyPI)
  • Affected versions: All versions through 0.9.0a1 (inclusive)
  • Fixed version: 0.9.0a2

Severity

  • CVSS Score: 9.1 (Critical)
  • Published Vector (CVSS v4.0): CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • Note: The vendor/CVE record published this score using the CVSS v4.0 standard; no separate CVSS v3.1 vector has been published for this CVE at the time of writing.

Mitigation and recommended actions

  • Immediate: Upgrade stigmem-node to version 0.9.0a2 or later, e.g. pip install --upgrade --pre stigmem-node (or pip install --upgrade --pre 'stigmem[node]' for the meta-package). The patched version introduces a pending-approval workflow so that peer tokens are not accepted until an administrator explicitly approves the peer using its expected fingerprint.
  • If immediate patching is not possible:
    • Restrict access to the federation peer registration endpoint to trusted, known network segments only.
    • Manually verify peer fingerprints out-of-band before allowing any federation peer relationship to be established.
    • Monitor federation peer registration logs for unexpected or unapproved peer registration attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge