Skip to main content
VulnerabilityPublished

CVE-2026-24897: ErugoOSS Erugo · Path Traversal

Affects ErugoOSS ErugoSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 10.0 Critical : upgrade to 0.2.15 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.2% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.15
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 28 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 27 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 11 minutes after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    Erugo 0.2.14 - Remote Code Execution (RCE)

    , 92 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Erugo and erugooss/Erugo to 0.2.15.

Affected software

ProductAffectedFixed in
ErugoOSSErugoAffected
  • <0.2.15
Fixed in
  • 0.2.15
GitHuberugooss/Erugopkg:github/erugooss/ErugoOther threatsAffected
  • <0.2.15
Fixed in
  • 0.2.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade all Erugo instances to version 0.2.15 or later, where the vulnerability is patched. Until upgrades are completed, restrict access to the Erugo platform to trusted users and networks only, employing network segmentation and firewall rules to limit exposure. Implement strict authentication and monitoring to detect unusual file upload activities or path traversal attempts. Conduct thorough audits of existing file shares and uploaded content to identify any unauthorized files or code. Employ application-layer security controls such as Web Application Firewalls (WAFs) configured to detect and block path traversal and code injection patterns. Additionally, enforce the principle of least privilege on user accounts to minimize potential damage from compromised low-privileged users. Regularly review and update incident response plans to include scenarios involving file upload and RCE attacks.

Description

CVE-2026-24897 is a critical path traversal vulnerability in Erugo, a self-hosted file-sharing platform, affecting versions prior to 0.2.15. An authenticated low-privileged user can exploit insufficient validation of user-supplied paths to upload arbitrary files anywhere on the server, including writable paths within the public web root. This enables remote code execution (RCE), allowing full compromise of the Erugo instance without requiring elevated privileges or user interaction. The vulnerability stems from improper limitation of pathname (CWE-22) and leads to code injection (CWE-94) and unrestricted file upload (CWE-434). Although no known exploits are reported in the wild yet, the CVSS 3.1 score is 10.0, reflecting the critical severity. Organizations using affected Erugo versions should upgrade to 0.

References

Community reviews

Loading reviews…