What is the CVSS score of CVE-2026-58499?

CVE-2026-58499 has a CVSS 3.1 base score of 8.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L. EPSS exploitation probability: 0.4%.

Which versions of Everos are affected by CVE-2026-58499?

EverOS by EverMind-AI (versions prior to 1.0.1) is vulnerable to unauthorized file modification attacks that do not require authentication or credentials.. A patch is available.

How to fix or mitigate CVE-2026-58499?

Within 24 hours: Identify all EverOS deployments and assess which instances have network-accessible API endpoints. Within 7 days: Monitor EverMind-AI security advisories for patch availability; if unavailable, implement firewall rules to restrict access to the POST /api/v1/memory/add endpoint. Within 30 days: Deploy patches immediately upon release; if unpatched, perform file integrity audits and escalate to vendor for remediation timeline.

Everos CVE-2026-58499

EUVD-2026-43038 HIGH

Path Traversal (CWE-22)

2026-07-10 GitHub_M

Path Traversal Everos

8.2

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

8.2 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

Low

Lifecycle Timeline

Patch available

Jul 10, 2026 - 22:02 EUVD

Analysis Generated

Jul 10, 2026 - 21:41 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Unauthenticated arbitrary file write in EverOS, an AI-agent memory runtime by EverMind-AI, affects all versions prior to 1.0.1 via the POST /api/v1/memory/add ingestion endpoint. Because the per-message sender_id field is not sanitized as a path-safe identifier (unlike app_id and project_id), an attacker can supply ../ sequences that redirect where extracted memory episodes are written, letting a remote unauthenticated caller create or overwrite .md files outside the memory root with partially attacker-controlled content. No public exploit identified at time of analysis, and no EPSS score was provided, but the CVSS 8.2 rating and unauthenticated network reach make it a meaningful integrity risk for exposed instances.