Skip to main content
VulnerabilityPublished

CVE-2026-28286: IceWhaleTech ZimaOS · External Control of File Name or Path

Affects IceWhaleTech ZimaOSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 30 Oct 2026, 06:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

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

What to do

Affected software

ProductAffectedFixed in
IceWhaleTechZimaOSAffected
  • =1.5.2-beta3
Fixed in–
GitHubicewhaletech/ZimaOSpkg:github/icewhaletech/ZimaOSOther threatsAffected
  • =1.5.2-beta3
Fixed in–

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

AI-suggested

  1. Immediately restrict API access to trusted and authenticated users only, employing strong authentication and network segmentation to limit exposure.
  2. Implement strict server-side validation of all file path inputs in the API to enforce path restrictions regardless of client-side controls.
  3. Monitor API usage logs for unusual file creation or modification requests targeting sensitive system directories.
  4. Employ host-based intrusion detection systems (HIDS) to detect unauthorized changes in critical directories.
  5. If possible, downgrade or avoid using version 1.5.2-beta3 until a patched version is released.
  6. Apply principle of least privilege to all users and services interacting with the API to minimize potential damage.
  7. Consider deploying application-layer firewalls or API gateways that can enforce path restrictions and validate requests before they reach the backend.
  8. Regularly back up critical system files and configurations to enable recovery in case of compromise.
  9. Engage with IceWhaleTech for updates on patches or official mitigations and apply them promptly once available.

Description

ZimaOS is a fork of CasaOS, an operating system for Zima devices and x86-64 systems with UEFI. In version 1.5.2-beta3, the application enforces restrictions in the frontend/UI to prevent users from creating files or folders in internal OS paths. However, when interacting directly with the API, the restrictions are bypass-able. By sending a crafted request targeting paths like /etc, /usr, or other sensitive system directories, the API successfully creates files or directories in locations where normal users should have no write access. This indicates that the API does not properly validate the target path, allowing unauthorized operations on critical system directories. No known patch is publicly available.

References

Community reviews

Loading reviews…