everos

GHSA-C795-2G9C-J48M

GHSA-C795-2G9C-J48M is a high-severity path traversal vulnerability in everos (pip), affecting versions <= 1.0.0. It is fixed in 1.0.1.

Key facts
CVSS score
8.2
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
everos
Fixed in
1.0.1
Disclosed
Not available

Summary

EverOS versions 1.0.0 and earlier are vulnerable to path traversal in the POST /api/v1/memory/add ingestion endpoint. The per-message senderid field was not validated as a path-safe identifier (unlike appid / projectid, which already enforced this). During user-memory extraction, senderid is used as the ownerid and joined into the filesystem path where the extracted episode is persisted as a Markdown file. A senderid containing ../ sequences could direct the write outside the configured memory root, allowing an unauthenticated caller to create or overwrite .md files at locations writable by the server process (unauthorized arbitrary file write). The file content is partially attacker-influenced. Patch: Fixed in v1.0.1 with (1) path-safe validation on sender_id (character whitelist plus rejection of the . and .. tokens) and (2) a defense-in-depth containment check in the Markdown writer that rejects any write resolving outside the memory root before any filesystem access, covering both the write and the append read-modify-write paths. Remediation: Upgrade to EverOS 1.0.1. There is no workaround for affected versions other than upgrading.

Impact

What is path traversal?

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Severity and exposure

GHSA-C795-2G9C-J48M has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (1.0.1). Upgrading removes the vulnerable code path.

Affected versions

pip

  • everos (<= 1.0.0)

Security releases

  • everos → 1.0.1 (pip)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether GHSA-C795-2G9C-J48M is reachable in your applications. Explore open-source security for your team.

See if GHSA-C795-2G9C-J48M is reachable in your applications. Get a demo

Already deployed Kodem? See GHSA-C795-2G9C-J48M in your environment

Remediation advice

Upgrade everos to 1.0.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about GHSA-C795-2G9C-J48M

What is GHSA-C795-2G9C-J48M?

GHSA-C795-2G9C-J48M is a high-severity path traversal vulnerability in everos (pip), affecting versions <= 1.0.0. It is fixed in 1.0.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is GHSA-C795-2G9C-J48M?

GHSA-C795-2G9C-J48M has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of everos are affected by GHSA-C795-2G9C-J48M?

everos (pip) versions <= 1.0.0 is affected.

Is there a fix for GHSA-C795-2G9C-J48M?

Yes. GHSA-C795-2G9C-J48M is fixed in 1.0.1. Upgrade to this version or later.

Is GHSA-C795-2G9C-J48M exploitable, and should I be worried?

Whether GHSA-C795-2G9C-J48M is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether GHSA-C795-2G9C-J48M is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-C795-2G9C-J48M?

Upgrade everos to 1.0.1 or later.

Stop the waste.
Protect your environment with Kodem.