# CVE-2025-64427: ZimaOS is vulnerable to Server-Side Request Forgery (SSRF)

> An authenticated local user can exploit insufficient URL validation in ZimaOS to access internal network services, potentially exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-m8hj-7xg5-p375

## What is CVE-2025-64427?

CVE-2025-64427 is a high-severity server-side request forgery vulnerability in IceWhaleTech ZimaOS, published on 2 Mar 2026. Any signed-in user can exploit it over the network, 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. In version 1.5.0 and prior, due to insufficient validation or restriction of target URLs, an authenticated local user can craft requests that target internal IP addresses (e.g., 127.0.0.1, localhost, or private network ranges). This allows the attacker to interact with internal HTTP/HTTPS services that are not intended to be exposed externally or to local users. No known patch is publicly available.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-64427?

It affects 1 product.


Products: Zimaspace Zimaos.

## How do I fix CVE-2025-64427?

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

## Is CVE-2025-64427 being exploited?

There is no known exploitation of CVE-2025-64427 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-28798](https://insights.sbomify.com/CVE-2026-28798/): Arbitrary internal service access via /v1/sys/proxy when Cloudflare Tunnel is enabled on ZimaOS (critical 9.1)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64427 and fix it if it is affected.

What it is: CVE-2025-64427 is a high-severity server-side request forgery vulnerability in IceWhaleTech ZimaOS, published on 2 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64427 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-2025-64427/ (Markdown: https://insights.sbomify.com/CVE-2025-64427/index.md)
```

## Sources

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

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