Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-gq6f-qwv9-rf4j

MEDIUM

GHSA-gq6f-qwv9-rf4j is a medium-severity (CVSS 6.5) vulnerability in mem0ai. O3 Security confirms whether GHSA-gq6f-qwv9-rf4j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

mem0 server lacks authentication and authorization controls for its memory deletion API endpoint

Also known asCVE-2026-31241PYSEC-2026-2634
Published
May 12, 2026
Updated
Jul 13, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Jul 13, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍mem0ai

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐍PyPImem0aiall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mem0ai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of mem0ai has shipped for GHSA-gq6f-qwv9-rf4j yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-gq6f-qwv9-rf4j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gq6f-qwv9-rf4j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.
O3 Security · Impact-Aware SCA

Is GHSA-gq6f-qwv9-rf4j in your dependencies?

O3 detects GHSA-gq6f-qwv9-rf4j across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-gq6f-qwv9-rf4j: mem0ai Denial of… | O3 Security