How to Fix CVE-2026-2754: NavBox (Bundle Sibling)
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-2754 is a sibling vulnerability in the same vendor advisory as CVE-2026-2752. Apply the same patched build and you close both. The technical detail below is what differs.
| Severity | 7.5 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | NavBox 4.12.0.3 |
| Fixed in | Same patched build as CVE-2026-2752 |
| Type (CWE) | CWE-306 Missing Authentication for Critical Function |
What's different about CVE-2026-2754?
Navtor NavBox exposes sensitive configuration and operational data due to missing authentication on HTTP API endpoints. An unauthenticated remote attacker with network access to the device can execute HTTP GET requests to TCP port 8080 to retrieve internal network parameters including ECDIS & OT Information, device identifiers, and service status logs.
How to fix CVE-2026-2754
Apply the patched build per the primary write-up: How to Fix CVE-2026-2752. All commands, verification steps, and rollback notes for NavBox are listed there.
Frequently asked questions
Does the CVE-2026-2752 patch close CVE-2026-2754?
Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.
Is CVE-2026-2754 listed in CISA KEV?
No public KEV listing at the time of this writing.
Where is the official advisory?
See https://www.navtor.com/navtor-vendor-statement
References
- Official vendor advisory: https://www.navtor.com/navtor-vendor-statement
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2754
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary: How to Fix CVE-2026-2752
*Written by Sai Kiran Pandrala. Part of the NavBox bundle. Full procedure at how-to-fix-cve-2026-2752.*