# CVE-2026-28798: Arbitrary internal service access via /v1/sys/proxy when Cloudflare Tunnel is enabled on ZimaOS

> Attackers can access internal localhost services via a proxy endpoint when Cloudflare Tunnel is enabled, exposing sensitive data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-vqqj-f979-8c8m

## What is CVE-2026-28798?

CVE-2026-28798 is a critical server-side request forgery vulnerability in IceWhaleTech ZimaOS, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZimaOS is a fork of CasaOS, an operating system for Zima devices and x86-64 systems with UEFI. Prior to version 1.5.3, a proxy endpoint (/v1/sys/proxy) exposed by ZimaOS's web interface can be abused (via an externally reachable domain using a Cloudflare Tunnel) to make requests to internal localhost services. This results in unauthenticated access to internal-only endpoints and sensitive local services when the product is reachable from the Internet through a Cloudflare Tunnel. This issue has been patched in version 1.5.3.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-28798?

It affects 1 product.


Products: Zimaspace Zimaos.

## How do I fix CVE-2026-28798?

No fix has been published for CVE-2026-28798 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-28798 being exploited?

There is no known exploitation of CVE-2026-28798 in the wild and no public exploit code.

## Other vulnerabilities in IceWhaleTech ZimaOS

- [CVE-2026-21891](https://insights.sbomify.com/CVE-2026-21891/): ZimaOS has Authentication Bypass via System-Level Username (critical 9.4)
- [CVE-2026-28442](https://insights.sbomify.com/CVE-2026-28442/): ZimaOS: Arbitrary Deletion of Internal System Files via API Path Manipulation (high 8.6)
- [CVE-2026-28286](https://insights.sbomify.com/CVE-2026-28286/): ZimaOS: Unauthorized Creation of Files/Folders in Restricted System Directories via API (high 8.6)
- [CVE-2024-48931](https://insights.sbomify.com/CVE-2024-48931/): ZimaOS Arbitrary File Read via Parameter Manipulation (high 7.5)
- [CVE-2024-49357](https://insights.sbomify.com/CVE-2024-49357/): ZimaOS (Installed Applications and System Information) has Unauthorized Sensitive Data Leak (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28798 and fix it if it is affected.

What it is: CVE-2026-28798 is a critical server-side request forgery vulnerability in IceWhaleTech ZimaOS, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28798 in the wild and no public exploit code.

Affected product: IceWhaleTech ZimaOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-28798/ (Markdown: https://insights.sbomify.com/CVE-2026-28798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28798
- OSV: https://osv.dev/vulnerability/CVE-2026-28798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-28798/
Summaries are generated and may contain mistakes; the official description above is the record.