# 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.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-c795-2g9c-j48m

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-58499?

2 open source packages ship an affected version, including everos.


| Package | Ecosystem | 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.

## Is CVE-2026-58499 being exploited?

There is no known exploitation of CVE-2026-58499 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58499 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-58499 in the wild and no public exploit code.

Affected packages and fixed versions:
- everos (PyPI): affected all versions; fixed in 1.0.1
- everos (PyPI): affected all versions; fixed in 1.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58499/ (Markdown: https://insights.sbomify.com/CVE-2026-58499/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58499
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58499
- OSV: https://osv.dev/vulnerability/CVE-2026-58499

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58499/
Summaries are generated and may contain mistakes; the official description above is the record.