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

Back
New CVE Detected

CVE-2026-76243 – Authentication Bypass / Unauthorized Read-Write Access – stigmem (stigmem-node) bef

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76243 is a critical improper authorization vulnerability (CWE-285) in stigmem, an open-source federated knowledge-fabric node implementation (PyPI package stigmem-node) maintained by eidetic-labs. Versions prior to 0.9.0a2 allow unauthenticated attackers to perform read, write, and federation operations using an anonymous identity when a node has authentication disabled and is exposed on a non-loopback network interface. The issue carries a CVSS score of 9.2 (Critical) and is remotely exploitable with no privileges or user interaction required.

Technical details

  • Root cause: When authentication is disabled on a stigmem node, the software does not restrict anonymous access to loopback/localhost interfaces, allowing anonymous identities to be trusted on any network-reachable deployment.
  • Trigger conditions: The node must be deployed with authentication disabled (an operator-selectable configuration) and bound/exposed to a non-loopback address (e.g., a LAN or internet-facing interface) rather than restricted to local development use.
  • Attack vector: Network (AV:N) — no authentication or user interaction is needed; an attacker who can reach the exposed node’s API can act as an anonymous but fully privileged client.
  • Impact: Unauthorized actors can read stored facts/data, write or modify data, and participate in federation operations (data exchange with other nodes) using an anonymous identity, resulting in high impact to confidentiality, integrity, and availability of the affected node and any federated data it exchanges.

Affected software

  • Product: stigmem / stigmem-node (PyPI package), maintained by eidetic-labs
  • Vulnerable versions: All versions prior to 0.9.0a2 (confirmed impacted: 0.9.0a1)
  • Fixed version: 0.9.0a2 and later

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade stigmem-node to version 0.9.0a2 or later (pip install --upgrade --pre stigmem-node).
  • If immediate patching is not possible:
    • Keep authentication enabled on any stigmem node that is not strictly confined to a local/loopback development environment.
    • Do not expose stigmem nodes with authentication disabled to any network beyond localhost/127.0.0.1.
    • Restrict network access to stigmem nodes using firewall rules, VPNs, or network segmentation until the fix is applied, especially for nodes participating in federation with other organizations.
    • Audit existing deployments for nodes running authentication-disabled configurations that are reachable from non-loopback interfaces.

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