dbcve.org
Navbox FirmwareOperating system · Navtor

CVE-2026-2754

HIGH · 7.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 4.16.2.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Navtor NavBox contains multiple HTTP API endpoints on TCP port 8080 that lack authentication checks, allowing any remote attacker to retrieve sensitive operational data including ECDIS & OT (Operational Technology) information, device identifiers, and service status logs without credentials.

MitigationImplement robust authentication and authorization controls on all HTTP API endpoints, preferably using industry-standard methods like OAuth 2.0 or mutual TLS, and restrict network access to trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Navbox FirmwareOperating system
Affected:>= 4.12.0.3, < 4.16.2.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm target is Navtor NavBox
    Access the HTTP API on port 8080 and look for NavBox-specific identifiers in the response (device type, service names, or Navtor branding in headers or JSON payloads)
    Affected if The device identifies itself as Navtor NavBox in API responses or HTTP headers
  2. Verify port 8080 is accessible
    Scan TCP port 8080 or attempt an HTTP request to http://<target>:8080
    Affected if Port 8080 accepts connections and returns HTTP responses
  3. Check firmware version
    Query the API endpoint for firmware version information, or check device status endpoints that expose version data
    Affected if Installed firmware version is >= 4.12.0.3 and < 4.16.2.4
  4. Test API endpoint access without credentials
    Send HTTP GET requests to common API paths on port 8080 (such as /status, /device, /info, /api endpoints) without providing any authentication headers or credentials
    Affected if API endpoints return HTTP 200 OK with sensitive data (ECDIS info, OT data, device identifiers, service logs) without requiring any authentication
  5. Verify sensitive data exposure
    Inspect responses from unauthenticated API calls for operational data including ECDIS information, OT details, device serial numbers, and service status logs
    Affected if The API returns ECDIS, OT information, device identifiers, or service status logs to unauthenticated requests

If the target is a Navtor NavBox with port 8080 exposed, firmware between 4.12.0.3 and 4.16.2.4, and HTTP API endpoints return sensitive operational data without any authentication, the environment is affected by CVE-2026-2754.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.16.2.4 or later
Fixed in 4.16.2.4
Interim mitigation

Implement robust authentication and authorization controls on all HTTP API endpoints, preferably using industry-standard methods like OAuth 2.0 or mutual TLS, and restrict network access to trusted sources.

Recommended fix Moderate confidence

Navbox Firmware 4.16.2.4 or later

  1. Identify the current Navbox Firmware version by accessing the device management interface or checking system information
  2. Download Navbox Firmware version 4.16.2.4 or later from the official Navtor vendor portal (www.navtor.com)
  3. Review vendor release notes and firmware upgrade instructions specific to Navbox device
  4. Perform a backup of current device configuration if supported
  5. Execute the vendor-provided firmware update procedure, typically via the device's web interface or dedicated update tool
  6. Verify the upgrade was successful by checking the new firmware version in the device management interface
  7. Confirm that HTTP API endpoints on TCP port 8080 now require authentication
Caveat Review vendor release notes for any configuration changes or compatibility considerations between current version and 4.16.2.4

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Navbox Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2754 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data