CVE-2026-58499 Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id
An unauthenticated attacker can exploit path traversal in EverOS to create or overwrite Markdown files outside the intended directory via the sender_id parameter.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-58499?
CVE-2026-58499 is a high-severity path traversal vulnerability in EverMind-AI EverOS, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
EverOS is a memory runtime for agents. Prior to 1.0.1, EverOS is vulnerable to path traversal in the POST /api/v1/memory/add ingestion endpoint because the per-message sender_id field was not validated as a path-safe identifier, unlike app_id and project_id. During user-memory extraction, sender_id is used as owner_id and joined into the filesystem path where the extracted episode is persisted as a Markdown file, so a sender_id containing ../ sequences could direct writes outside the configured memory root and allow an unauthenticated caller to create or overwrite .md files at locations writable by the server process with partially attacker-influenced content. This issue is fixed in version 1.0.1.
Weakness: CWE-22
Which versions are affected by CVE-2026-58499?
2 open source packages ship an affected version, including everos.
| Package | Affected | Fixed in |
|---|---|---|
everos PyPI | All versions | 1.0.1 |
everos PyPI | All versions | 1.0.1 |
How do I fix CVE-2026-58499?
Upgrade everos to 1.0.1 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-58499 being exploited?
There is no known exploitation of CVE-2026-58499 in the wild and no public exploit code.
Sources
Also known as GHSA-c795-2g9c-j48m.