What’s Vulnerable › Vulnerabilities

CVE-2026-58499: Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id

• Severity: high (CVSS 8.2 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-10 · updated 2026-10-25
• Weakness: CWE-22

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.

Affected products

• EverMind-AI EverOS: before 1.0.1

References

• https://github.com/EverMind-AI/EverOS/commit/a10cdcd197747f371b7879a32c2cc3f77471e9c2
• https://github.com/EverMind-AI/EverOS/releases/tag/v1.0.1
• https://github.com/EverMind-AI/EverOS/security/advisories/GHSA-c795-2g9c-j48m

Get alerted when CVE-2026-58499 or the next vulnerability affects your stack