Security readout for executives and security teams
Plain-English summary
CVE-2026-24897 lets a low-privileged Erugo user upload files into sensitive server locations, including the public web root. If abused, that uploaded file can run code on the server and fully compromise the Erugo instance. Erugo 0.2.15 is identified as the fixed version.
Executive priority
Treat as urgent for any Erugo deployment. A compromised file-sharing server can expose stored files, credentials, and connected systems. Patch quickly, especially if external users or broad internal user groups can access Erugo.
Technical view
Erugo versions before 0.2.15 insufficiently validate user-supplied paths when creating shares. This enables arbitrary file upload to attacker-specified writable locations, including executable web-accessible paths, leading to remote code execution. The record maps to CWE-22, CWE-434, and CWE-94. The bundle notes authenticated low-privileged abuse, though the CVSS vector lists PR:N.
Likely exposure
Organizations running self-hosted Erugo versions up to and including 0.2.14 are potentially exposed. Risk is highest where untrusted or many low-privileged users can authenticate and create shares.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The issue is still high urgency because the advisory describes full instance compromise through a low-complexity upload/path validation flaw.
Researcher notes
Primary evidence is the GitHub advisory, release, and fixing commit. Note the authentication ambiguity: the description says low-privileged authenticated user, while the supplied CVSS vector says PR:N. Validate against the advisory before modeling unauthenticated exposure.
Mitigation direction
- Upgrade Erugo to version 0.2.15 or later.
- Review the GitHub security advisory and release notes for vendor guidance.
- Limit Erugo access to trusted users until patched.
- Back up configuration and data before applying the update.
Validation and detection
- Inventory all self-hosted Erugo deployments.
- Confirm each Erugo instance is running version 0.2.15 or later.
- Review application logs for suspicious share creation or unusual upload paths.
- Inspect public web-root locations for unexpected uploaded files.
- Verify low-privileged users cannot choose arbitrary server paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24897 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ErugoOSS/Erugo/security/advisories/GHSA-336w-hgpq-6369CVE reference · x_refsource_CONFIRM
- https://github.com/ErugoOSS/Erugo/commit/256bc63831a0b5e9a94cb024a0724e0cd5fa5e38CVE reference · x_refsource_MISC
- https://github.com/ErugoOSS/Erugo/releases/tag/v0.2.15CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.