CVE-2026-75110

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-17. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

MemOS is a memory operating system for LLMs and AI agents. In deployments where authentication is enabled (AUTH_ENABLED=true) but the undocumented, defaultless INTERNAL_SERVICE_SECRET environment variable is unset, the is_internal_request() check in src/memos/api/middleware/auth.py fails open: os.getenv("INTERNAL_SERVICE_SECRET") returns None and a request omitting the X-Internal-Service header also yields None, so the comparison None == None evaluates true. The request is then treated as a trusted internal principal and granted scopes: ["all"]. As a result, an unauthenticated remote attacker can reach the admin API-key management endpoints to mint API keys for any user, enumerate keys, revoke keys, and generate a master key for persistent privileged access, as well as all data endpoints.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Authentication bypass in MemOS server: internal-service check fails open when INTERNAL_SERVICE_SECRET is unset · Issue #2259 · MemTensor/MemOS · GitHub

https://github.com/MemTensor/MemOS/issues/2259
generic

MemOS Authentication Bypass via Unset INTERNAL_SERVICE_SECRET | Advisories | VulnCheck

https://www.vulncheck.com/advisories/memos-authentication-bypass-via-unset-internal-service-secret
generic

MemOS/src/memos/api/middleware/auth.py at main · MemTensor/MemOS · GitHub

https://github.com/MemTensor/MemOS/blob/main/src/memos/api/middleware/auth.py
generic

GitHub - MemTensor/MemOS: Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings and DeepSeek Harness support. · GitHub

https://github.com/MemTensor/MemOS

Vendor Advisories for CVE-2026-75110(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 07:42 UTCGHSA enrichment
  2. 2026-08-21 03:18 UTCEG score recompute
  3. 2026-08-21 03:17 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:52 UTCGHSA enrichment
  6. 2026-08-20 18:28 UTCGHSA enrichment
  7. 2026-08-20 14:04 UTCGHSA enrichment
  8. 2026-08-20 09:40 UTCGHSA enrichment
  9. 2026-08-20 05:16 UTCGHSA enrichment
  10. 2026-08-20 00:51 UTCGHSA enrichment
  11. 2026-08-19 20:24 UTCEG score recompute
  12. 2026-08-19 20:24 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 15:56 UTCGHSA enrichment
  15. 2026-08-19 11:31 UTCGHSA enrichment
  16. 2026-08-19 07:06 UTCGHSA enrichment
  17. 2026-08-19 02:41 UTCGHSA enrichment
  18. 2026-08-18 22:14 UTCGHSA enrichment
  19. 2026-08-18 17:49 UTCEG score recompute
  20. 2026-08-18 17:49 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:23 UTCEG score recompute
  24. 2026-08-18 13:22 UTCGHSA enrichment
  25. 2026-08-18 13:06 UTCEG score recompute
Show 10 more
  1. 2026-08-18 13:06 UTCGHSA enrichment
  2. 2026-08-18 11:30 UTCEG score recompute
  3. 2026-08-18 11:30 UTCGHSA enrichment
  4. 2026-08-18 10:45 UTCGHSA enrichment
  5. 2026-08-18 06:20 UTCGHSA enrichment
  6. 2026-08-18 01:55 UTCGHSA enrichment
  7. 2026-08-17 21:31 UTCEG score recompute
  8. 2026-08-17 21:31 UTCGHSA enrichment
  9. 2026-08-17 20:45 UTCEG score recompute
  10. 2026-08-17 20:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75110?
CVE-2026-75110 is a critical vulnerability published on August 17, 2026. MemOS is a memory operating system for LLMs and AI agents. In deployments where authentication is enabled (AUTHENABLED=true) but the undocumented, defaultless INTERNALSERVICESECRET environment variable is unset, the isinternalrequest() check in src/memos/api/middleware/auth.py fails open:…
When was CVE-2026-75110 disclosed?
CVE-2026-75110 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75110 actively exploited?
CVE-2026-75110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-75110?
CVE-2026-75110 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-75110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75110, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75110

Explore →

Is Your Infrastructure Affected by CVE-2026-75110?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs