Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By icscert

  2. · 33 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-5087, by who scored it
Scored byCVSSScoreVector
icscertCNA (assigner)4.0Medium6.0CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0Medium6.0CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.0.

Affected products

What to do

Solution: Kaleris recommends users to implement the following versions or later: * Navis N4: Version 3.1.44+ * Navis N4: Version 3.2.26+ * Navis N4: Version 3.3.27+ * Navis N4: Version 3.4.25+ * Navis N4: Version 3.5.18+ * Navis N4: Version 3.6.14+ * Navis N4: Version 3.7.0+ * Navis N4: Version 3.8.0+ If users are unable to update, Kaleris recommends following these mitigations: * If N4 does not need to be exposed to the internet, placing it behind a firewall. * If CAP needs to be exposed to the internet, disable the Ultra Light Client on the nodes being exposed. This can be done by blocking the Ultra Light Client URLs in the load balancer or firewall by blocking the following patterns: "url-pattern*.jnlp</url-pattern" and "url-pattern/ulc</url-pattern" * The Ultra Light Client endpoint can also be disabled on the N4 Cluster node by commenting out relevant code in the web.xml file and restarting the server. * If the Ultra Light Client must be exposed to the Internet, do one of the following: a. Set up a secure VPN connection to allow access for known external parties. b. Set up an authenticated jump system (Citrix, VDI, Etc.). c. Whitelist external allowed IPs. (least secure option) * Additionally, the following controls should be applied: a. Restrict the number of N4 nodes exposed to the internet. b. Ensure that HTTPS is enabled and configured on the filewall/loadbalancer. c. Use a reliable third-party party firewall with built in DDOS protection that can detect unwanted intrusions. * Users are required to implement TLS in their load balancer. The setup for this is included in the Application Security Guide that is provided to all users. * A final option to consider is upgrading to N4 4.0, where the Ultra Light Client has been fully replaced with the HTML UI. Kaleris has sent a security advisory to all customers running Kaleris software. For more information, users should email [email protected]

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-5087 badge
[![CVE-2025-5087](https://cveledger.app/badge/CVE-2025-5087.svg)](https://cveledger.app/cve/CVE-2025-5087)

Record last updated .