CVE-2026-82673
Path traversal in ash_admin file upload allows arbitrary file write as BEAM user.
Is CVE-2026-82673 being exploited?
Not confirmed. CVE-2026-82673 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.59% probability of exploitation in the next 30 days.
How severe is CVE-2026-82673?
CVE-2026-82673 is rated High with a CVSS score of 8.3. 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-82673?
Yes. A fix has been recorded for CVE-2026-82673. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82673 affect?
CVE-2026-82673 affects ash_admin >=0.13.7 and <1.3.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82673?
Upgrade to ash_admin v1.3.1 immediately; or sanitize filenames (Path.basename) and restrict upload paths.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unsanitized upload filename enables path traversal and arbitrary file write; attacker can overwrite assets/config/cron/ssh to achieve RCE as BEAM user.
Immediate action required
- affected>= 0.13.7 and < 1.3.1
- affected>= e8f496b6a064ad67dc1cd30433e5921d2192d254 and < 4bb41cb697f3d9be58462d727aed75aba76efc82
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.