# CVE-2025-5087: Cleartext Transmission of Sensitive Information in Kaleris Navis N4

> Attackers can intercept network traffic to extract plaintext credentials from Kaleris Navis N4 Ultra Light Clients due to insecure HTTP transmission.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-wq9q-jvph-86fj

## What is CVE-2025-5087?

CVE-2025-5087 is a medium-severity vulnerability in Kaleris Navis N4, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Kaleris NAVIS N4 ULC (Ultra Light Client) communicates insecurely using zlib-compressed data over HTTP. An attacker capable of observing network traffic between Ultra Light Clients and N4 servers can extract sensitive information, including plaintext credentials.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-5087 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5087 is a medium-severity vulnerability in Kaleris Navis N4, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-5087 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-5087/ (Markdown: https://insights.sbomify.com/CVE-2025-5087/index.md)
```

## Sources

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

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