Approved changes feed: RSS · Atom
cpe:2.3:a:evermind-ai:everos:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Evermind Ai (3fd8a1d5-f943-5beb-8ce6-59f6fc2e5e5b) |
|---|---|
| Product | Everos (d8935b50-34f9-5ee2-b747-e00a540a5a1f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-58499 |
vulnerable | 2026-07-29 01:03:16.872609 |
Path traversal in EverOS /api/v1/memory/add via unvalidated sender_id
HIGH (8.2)
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.
Published: 2026-07-10T20:53:24.196Z
Updated: 2026-07-13T16:18:18.609Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.