Unauthorized Markdown writes via unvalidated sender identifier
Published Jul 10, 2026 · Updated Jul 10, 2026
Path traversal in EverOS before 1.0.1 allows remote attackers to create or overwrite Markdown files through its memory ingestion API. The POST /api/v1/memory/add handler reuses an unvalidated sender_id as owner_id when constructing the episode path. No authentication or user interaction is required, but fresh installations bind the API to loopback; writes are limited to .md paths writable by the server process and contain partially attacker-controlled content.
Summary
What happened
Path traversal in EverOS before 1.0.1 allows remote attackers to create or overwrite Markdown files through its memory ingestion API. The POST /api/v1/memory/add handler reuses an unvalidated sender_id as owner_id when constructing the episode path. No authentication or user interaction is required, but fresh installations bind the API to loopback; writes are limited to .md paths writable by the server process and contain partially attacker-controlled content.
The record
- CVE
- CVE-2026-58499
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- EverMind
- Product
- EverOS
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo