Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/EverMind-AI/EverOS/commit/a10cdcd197747f371b7879a32c2cc3f7747
- https://github.com/EverMind-AI/EverOS/releases/tag/v1.0.1
- https://github.com/EverMind-AI/EverOS/security/advisories/GHSA-c795-2g9c-j48m
FAQ
What is CVE-2026-58499?
CVE-2026-58499 is a vulnerability with a CVSS score of 8.2 (HIGH). 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 validate...
How severe is CVE-2026-58499?
CVE-2026-58499 has been rated HIGH with a CVSS base score of 8.2/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-58499?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.