CVE-2026-24897 json
Authenticated Remote Code Execution via Arbitrary File Upload
published 2026-01-28 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-4975
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 1
- Exploit-DB
Summary
Erugo is a self-hosted file-sharing platform. In versions up to and including 0.2.14, an authenticated low-privileged user can upload arbitrary files to any specified location due to insufficient validation of user‑supplied paths when creating shares. By specifying a writable path within the public web root, an attacker can upload and execute arbitrary code on the server, resulting in remote code execution (RCE). This vulnerability allows a low-privileged user to fully compromise the affected Erugo instance. Version 0.2.15 fixes the issue.
Patch / fix
Timeline
- Published
- First public exploit (EDB-52529)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9 mo ago
Exploit prediction
3.27% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-52529 Erugo 0.2.14 - Remote Code Execution (RCE) webapps, 2026-04-30
- github.com https://github.com/ErugoOSS/Erugo/security/advisories/GHSA-336w-hgpq-6369 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- ErugoOSS Erugo
Classification
References
-
github.com
/ErugoOSS/Erugo/commit/256bc63831a0b5e9a94cb024a0724e0cd5fa5e38
patch
-
github.com
/ErugoOSS/Erugo/security/advisories/GHSA-336w-hgpq-6369
exploit, vendor-advisory
-
github.com
/ErugoOSS/Erugo/releases/tag/v0.2.15
release-notes
Sources
- CVE List CVE-2026-24897
- NVD CVE-2026-24897
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.