CVE-2026-58499

Received Received - Intake

Path Traversal in EverOS Memory Runtime

Publication date: 2026-07-10

Last updated on: 2026-07-10

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-10

Last Modified

2026-07-10

Generated

2026-07-11

AI Q&A

2026-07-11

EPSS Evaluated

N/A

NVD

CVE-2026-58499

Affected Vendors & Products

Vendor	Product	Version / Range
everos	everos	to 1.0.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

EverOS is a memory runtime for agents that had a vulnerability prior to version 1.0.1 in its POST /api/v1/memory/add ingestion endpoint. The issue was due to the sender_id field not being validated as a path-safe identifier, unlike other fields such as app_id and project_id.

Because sender_id was used as owner_id and incorporated into the filesystem path where extracted memory episodes are saved as Markdown files, an attacker could include '../' sequences in sender_id to perform a path traversal attack.

This allowed an unauthenticated attacker to write or overwrite .md files outside the intended memory root directory, potentially placing files in locations writable by the server process with content partially controlled by the attacker.

The vulnerability was fixed in EverOS version 1.0.1.

Impact Analysis

This vulnerability can allow an unauthenticated attacker to create or overwrite Markdown files on the server outside the intended directory.

Because the attacker can influence the content of these files, this could lead to unauthorized data modification or potentially enable further attacks depending on how these files are used by the system.

The impact includes integrity loss of data (high impact on integrity) and partial denial of service (low impact on availability), as indicated by the CVSS score.

Mitigation Strategies

The vulnerability is fixed in EverOS version 1.0.1. Immediate mitigation involves upgrading EverOS to version 1.0.1 or later.

Until the upgrade can be applied, restrict access to the POST /api/v1/memory/add ingestion endpoint to trusted users only, as the vulnerability allows unauthenticated callers to exploit path traversal.

Hi! I’m here to help you understand CVE-2026-58499. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70