Skip to content
Applications

CVE-2026-49948

8.6
High
EPSS 0.29%Patch availableJun 10, 2026

Auth bypass on /configure lets any authenticated user redirect LLM/embedder traffic to attacker.

triage
server-sideruntimeWAF · ineffectiveAV · networkCWE-862· Missing Authorization

WAF coverage: Missing authorization.

Also consider: patch

cvss vector
attack vectornetworkattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
common questions

Is CVE-2026-49948 being exploited?

Not confirmed. CVE-2026-49948 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-49948?

CVE-2026-49948 is rated High with a CVSS score of 8.6. 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-49948?

Yes. A fix has been recorded for CVE-2026-49948. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49948 affect?

CVE-2026-49948 affects Mem0 self-hosted server (versions <= 0.2.8). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49948?

Upgrade to 0.2.9+; enforce role checks on /configure; rotate API keys.

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

executive summary
technical analysis
affected
Mem0 self-hosted server (versions <= 0.2.8)
impact

Attacker can redirect all LLM/embedder traffic to a controlled server; config persists in PostgreSQL across restarts.

action required

Patch when possible

affected versions
mem0ai mem0
  • affected<= 0.2.8
vendor says fixed inae7f4062652df1376990221101d1adbb0819c973

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