dbcve.org
Navbox FirmwareOperating system · Navtor

CVE-2026-2752

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 4.16.2.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 allows information disclosure via the /api/ais-data endpoint. A remote, unauthenticated attacker can send crafted requests to trigger an unhandled exception, causing the server to return verbose .NET stack traces. These error messages expose internal class names, method calls, and third-party library references (e.g., System.Data.SQLite), which may assist attackers in mapping the application's internal structure.

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 · moderate confidence

Navtor NavBox exposes verbose .NET stack traces through the /api/ais-data endpoint when crafted requests trigger unhandled exceptions. Remote, unauthenticated attackers can receive detailed error messages revealing internal class names, method signatures, and third-party library references (e.g., System.Data.SQLite), enabling reconnaissance of the application's internal architecture.

MitigationImplement proper exception handling in the /api/ais-data endpoint and configure the application to return generic error responses in production environments, preventing stack trace disclosure.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Navtor NavBox presence
    Confirm the target system is a Navtor NavBox device. This is typically an AIS (Automatic Identification System) transponder or navigation device. Check device documentation, network inventory, or access the device's web interface if available.
    Affected if The system is a Navtor NavBox device
  2. Check firmware version
    Access the device's administrative interface or check system information to find the installed firmware version. Compare it to the affected range: >= 4.12.0.3 and < 4.16.2.4.
    Affected if Firmware version falls within 4.12.0.3 through 4.16.2.3 (inclusive)
  3. Verify API endpoint accessibility
    Attempt to access the /api/ais-data endpoint on the NavBox device. This typically requires an HTTP request to the device's IP address on the appropriate port.
    Affected if The /api/ais-data endpoint is reachable and responds to requests
  4. Test for stack trace disclosure
    Send a crafted request to /api/ais-data that may trigger an unhandled exception. For example, send malformed input, missing parameters, or unexpected data formats. Inspect the HTTP response for .NET stack traces, class names, method signatures, or library references.
    Affected if Response contains detailed .NET stack traces, internal class names (e.g., System.Data.SQLite), or method signatures

User is affected if NavBox firmware version is between 4.12.0.3 and 4.16.2.3 and the /api/ais-data endpoint returns verbose stack traces in response to malformed requests.

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 proper exception handling in the /api/ais-data endpoint and configure the application to return generic error responses in production environments, preventing stack trace disclosure.

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 settings
  2. Download Navbox Firmware version 4.16.2.4 or later from the official Navtor vendor (www.navtor.com) or authorized distribution channel
  3. Backup current device configuration if the web interface provides a configuration export feature
  4. Access the device administrative interface and navigate to the firmware update section
  5. Upload the firmware file (version 4.16.2.4 or later) and initiate the update process
  6. Wait for the device to reboot and complete the update
  7. Verify the update was successful by checking the firmware version in the device settings
  8. Test the /api/ais-data endpoint to confirm stack traces are no longer exposed in error responses
Caveat Standard firmware update; ensure backup of configuration and plan for brief downtime during update process

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2752 — 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-2752 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