Skip to content
AI/ML

CVE-2026-75110

9.3
Critical
EPSS 0.52%Aug 18, 2026

Auth bypass in MemOS lets unauthenticated actors access admin API and mint keys.

common questions

Is CVE-2026-75110 being exploited?

Not confirmed. CVE-2026-75110 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-75110?

CVE-2026-75110 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-75110?

Not known from our data. No patch reference has been recorded for CVE-2026-75110, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-75110 affect?

CVE-2026-75110 affects MemOS, MemOS deployments with AUTH_ENABLED=true, Instances missing INTERNAL_SERVICE_SECRET, LLM/AI agent platforms using MemOS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75110?

Set INTERNAL_SERVICE_SECRET, rotate/revoke keys, restrict network access, apply vendor patch when available

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MemOSMemOS deployments with AUTH_ENABLED=trueInstances missing INTERNAL_SERVICE_SECRETLLM/AI agent platforms using MemOS
impact

Remote unauthenticated attacker can mint/revoke API keys, generate a master key, and access all data and admin endpoints.

action required

Immediate action required

affected versions
MemTensor MemOS
  • affected<= 2.0.30

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free