# CVE-2025-2566: Deserialization of Untrusted Data in Kaleris Navis N4

> An unauthenticated attacker can execute arbitrary code on Kaleris Navis N4 servers via unsafe Java deserialization in the Ultra Light Client.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-8jgr-qfg7-w699

## What is CVE-2025-2566?

CVE-2025-2566 is a critical unsafe deserialization vulnerability in Kaleris Navis N4, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kaleris NAVIS N4 ULC (Ultra Light Client) contains an unsafe Java deserialization vulnerability. An unauthenticated attacker can make specially crafted requests to execute arbitrary code on the server.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2025-2566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2566 is a critical unsafe deserialization vulnerability in Kaleris Navis N4, published on 24 Jun 2025. 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-2025-2566 in the wild and no public exploit code.

Affected product: Kaleris Navis N4. 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-2566/ (Markdown: https://insights.sbomify.com/CVE-2025-2566/index.md)
```

## Sources

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

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