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

Back
New CVE Detected

CVE-2026-75110 – Authentication Bypass / Full Admin Takeover – MemOS (MemTensor) ≤ 2.0.30

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75110 is a critical authentication bypass vulnerability in MemOS, the open-source memory operating system for LLMs and AI agents developed by MemTensor. The flaw exists in the internal request-trust logic of the authentication middleware and allows a completely unauthenticated remote attacker to obtain full administrative (scopes: ["all"]) access to the API. It affects deployments with authentication enabled (AUTH_ENABLED=true), and carries a CVSS v3.1 base score of 9.8 (Critical) / CVSS v4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The is_internal_request() function in src/memos/api/middleware/auth.py determines whether an incoming request should be treated as a trusted internal service call by comparing the value of the X-Internal-Service request header against the INTERNAL_SERVICE_SECRET environment variable.
  • Trigger condition: If the operator enables authentication (AUTH_ENABLED=true) but never sets INTERNAL_SERVICE_SECRET (an undocumented variable, so many deployments omit it), os.getenv("INTERNAL_SERVICE_SECRET") returns None. A request that simply omits the X-Internal-Service header also resolves to None. The comparison None == None evaluates to True, so the check "fails open" instead of failing closed.
  • Attack vector: Network — no credentials, headers, or prior access are required. An attacker only needs to send a plain HTTP request to a reachable MemOS API instance.
  • Impact: The request is classified as an internal/trusted service call and is granted scopes: ["all"]. This lets an unauthenticated attacker:
    • Mint new API keys for any user
    • Enumerate existing API keys
    • Revoke API keys (denial of service)
    • Generate master keys for persistent, long-term access
    • Access administrative (/admin/*) endpoints and all data endpoints, exposing stored agent/user memory data
  • Classification: CWE-697 (Incorrect Comparison).

Affected software

  • Vendor/Project: MemTensor — MemOS
  • Package: pkg:pypi/MemoryOS
  • Affected versions: All versions from the initial release through 2.0.30, when deployed with AUTH_ENABLED=true and INTERNAL_SERVICE_SECRET left unset.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: As of this writing, no patched MemOS release has been published; the fix is tracked as in-progress in the upstream GitHub issue (MemTensor/MemOS #2259). Security teams should monitor the MemTensor/MemOS repository and upgrade to the fixed release as soon as it becomes available.
  • Workarounds / network mitigations (until a patch ships):
    • Explicitly set INTERNAL_SERVICE_SECRET to a strong, randomly generated value in every environment where AUTH_ENABLED=true — never leave it unset.
    • Ensure the X-Internal-Service header cannot be set or spoofed by external/untrusted clients; strip or block this header at the reverse proxy/load balancer for any request originating outside the trusted internal network.
    • Restrict network exposure of MemOS API endpoints (especially /admin/* and data/memory endpoints) so they are not reachable from the public internet; place them behind a VPN, firewall allowlist, or internal-only network segment.
    • Audit existing API keys and master keys for unexpected or unrecognized entries, and rotate all API keys and any INTERNAL_SERVICE_SECRET-dependent credentials as a precaution.
    • Monitor logs for API key creation, master key generation, or admin endpoint access originating from unexpected source IPs.

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