{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-58499","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2026-06-30T20:21:25.813Z","datePublished":"2026-07-10T20:53:24.196Z","dateUpdated":"2026-07-10T20:53:24.196Z"},"containers":{"cna":{"title":"Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id","problemTypes":[{"descriptions":[{"cweId":"CWE-22","lang":"en","description":"CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":8.2,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L","version":"3.1"}}],"references":[{"name":"https://github.com/EverMind-AI/EverOS/security/advisories/GHSA-c795-2g9c-j48m","tags":["x_refsource_CONFIRM"],"url":"https://github.com/EverMind-AI/EverOS/security/advisories/GHSA-c795-2g9c-j48m"},{"name":"https://github.com/EverMind-AI/EverOS/commit/a10cdcd197747f371b7879a32c2cc3f77471e9c2","tags":["x_refsource_MISC"],"url":"https://github.com/EverMind-AI/EverOS/commit/a10cdcd197747f371b7879a32c2cc3f77471e9c2"},{"name":"https://github.com/EverMind-AI/EverOS/releases/tag/v1.0.1","tags":["x_refsource_MISC"],"url":"https://github.com/EverMind-AI/EverOS/releases/tag/v1.0.1"}],"affected":[{"vendor":"EverMind-AI","product":"EverOS","versions":[{"version":"< 1.0.1","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2026-07-10T20:53:24.196Z"},"descriptions":[{"lang":"en","value":"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."}],"source":{"advisory":"GHSA-c795-2g9c-j48m","discovery":"UNKNOWN"}}}}