CVE-2026-58499
Unauthenticated path traversal in EverOS allows arbitrary .md file writes.
Is CVE-2026-58499 being exploited?
Not confirmed. CVE-2026-58499 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-58499?
CVE-2026-58499 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58499?
Yes. A fix has been recorded for CVE-2026-58499. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58499 affect?
CVE-2026-58499 affects EverOS < 1.0.1, EverOS memory runtime, EverOS agents. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58499?
Upgrade to EverOS 1.0.1; sanitize sender_id and restrict file-write permissions
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can use ../ in sender_id to create/overwrite .md files outside memory root, enabling data tampering, file overwrite, or potential code/data injection.
Immediate action required
- affected< 1.0.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.