Vulnerabilities in pkg:pypi/everos
PACKAGEGHSA-c795-2g9c-j48m is a HIGH (CVSS 8.2) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting EverOS libraries in the PyPI ecosystem. The issue involves path traversal in everos /api/v1/memory/add via unvalidated sender_id. Remediation is available by upgrading affected packages to version 1.0.1.
pkg:pypi/everos
Vulnerability advisories affecting package pkg:pypi/everos. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-c795-2g9c-j48m | - | HIGH | EverOS: Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id |
GHSA-c795-2g9c-j48m at a Glance
Security Impact
CVSS: 8.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L).
How to Fix GHSA-c795-2g9c-j48m
To remediate this vulnerability, upgrade all affected EverOS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install everos>=1.0.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show everos
How to Check if You Are Affected
To determine whether your Python environment is affected by GHSA-c795-2g9c-j48m, inspect your installed packages using pip:
pip show everos
Analyze the terminal output to locate any version of EverOS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.1), your application is affected.
Note: The pip show everos command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where 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. In EverOS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-c795-2g9c-j48m Affected EverOS Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
everos
|
PyPI |
< 1.0.1
|
1.0.1
|
References
Frequently Asked Questions
What is GHSA-c795-2g9c-j48m?
Which EverOS versions are affected?
What version fixes GHSA-c795-2g9c-j48m?
Is everos affected?
What is the CVSS score of GHSA-c795-2g9c-j48m?
What CWE is associated with GHSA-c795-2g9c-j48m?
How can I check PyPI dependencies for GHSA-c795-2g9c-j48m?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c795-2g9c-j48m",
"modified" : "2026-06-19T21:43:12Z",
"published" : "2026-06-19T21:43:12Z",
"aliases" : [ ],
"summary" : "EverOS: Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id",
"details" : "EverOS versions 1.0.0 and earlier are vulnerable to path traversal in the POST /api/v1/memory/add ingestion endpoint. The per-message sender_id field was not validated as a path-safe identifier (unlike app_id / project_id, which already enforced this). During user-memory extraction, sender_id is used as the owner_id and joined into the filesystem path where the extracted episode is persisted as a Markdown file. A sender_id 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.\n\n**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.\n\n**Remediation**: Upgrade to EverOS 1.0.1. There is no workaround for affected versions other than upgrading.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "everos"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.0.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.0.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/EverMind-AI/EverOS/security/advisories/GHSA-c795-2g9c-j48m"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/EverMind-AI/EverOS"
}, {
"type" : "WEB",
"url" : "https://github.com/EverMind-AI/EverOS/releases/tag/v1.0.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-19T21:43:12Z",
"nvd_published_at" : null
}
}