Vulnerability Database · Maven · Package report

com.graphhopper:graphhopper-nav: vulnerability history, versions and safety

com.graphhopper:graphhopper-nav is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 7 releases, first recorded in May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on com.graphhopper:graphhopper-nav 12.0-pre2 i

Updated on 23 Oct 2026

Good news: 12.0-pre2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 12.0-pre2 or newer. This can change: a vulnerability disclosed tomorrow can affect 12.0-pre2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 12.0-pre2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 19 May 2021 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 6,737 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.graphhopper:graphhopper-nav, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
11.1 29 Sep 2026 none Apache-2.0 — Details →
12.0-pre2 29 Sep 2026 none Apache-2.0 — Details →
11.0 14 Oct 2025 none Apache-2.0 — Details →
10.2 20 Jan 2025 none Apache-2.0 — Details →
10.1 17 Jan 2025 none Apache-2.0 — Details →
10.0 04 Nov 2024 none Apache-2.0 — Details →
9.1 05 May 2024 none Apache-2.0 — Details →
9.0 22 Apr 2024 none Apache-2.0 — Details →
9.0-pre1 22 Nov 2023 none Apache-2.0 — Details →
8.0 17 Oct 2023 none Apache-2.0 — Details →
7.0 13 Mar 2023 none Apache-2.0 — Details →
7.0-pre2 09 Dec 2022 none Apache-2.0 — Details →
7.0-testgithub6 08 Dec 2022 none Apache-2.0 — Details →
7.0-testgithub4 08 Dec 2022 none Apache-2.0 — Details →
7.0-testgithub3 08 Dec 2022 none Apache-2.0 — Details →
6.2 23 Oct 2022 none Apache-2.0 — Details →
6.1 14 Oct 2022 none Apache-2.0 — Details →
7.0-pre1 14 Oct 2022 none Apache-2.0 — Details →
6.0 13 Sep 2022 none Apache-2.0 — Details →
5.3 29 Apr 2022 none Apache-2.0 — Details →
5.0 23 Mar 2022 none Apache-2.0 — Details →
5.0-pre3 08 Mar 2022 none Apache-2.0 — Details →
5.0-pre2 04 Mar 2022 none Apache-2.0 — Details →
5.0-pre1 21 Feb 2022 none Apache-2.0 — Details →
4.0 29 Sep 2021 none Apache-2.0 — Details →
4.0-pre2 22 Jul 2021 none Apache-2.0 — Details →
3.2 21 Jul 2021 none Apache-2.0 — Details →
4.0-pre1 14 Jun 2021 none Apache-2.0 — Details →
3.0 17 May 2021 none Apache-2.0 — Details →
3.0-pre5 10 May 2021 none Apache-2.0 — Details →
2.4 05 May 2021 none Apache-2.0 — Details →
3.0-pre4 28 Apr 2021 none Apache-2.0 — Details →
client_hc_no_vehicle 19 Apr 2021 M1 Apache-2.0 Yes Details →
3.0-pre3 31 Mar 2021 none Apache-2.0 — Details →
3.0-pre2 25 Feb 2021 none Apache-2.0 — Details →
3.0-pre1 29 Jan 2021 none Apache-2.0 — Details →
2.3 27 Nov 2020 M1 Apache-2.0 Yes Details →
2.2 12 Nov 2020 M1 Apache-2.0 Yes Details →
2.1 12 Oct 2020 M1 Apache-2.0 Yes Details →
2.0 29 Sep 2020 M1 Apache-2.0 Yes Details →
2.0-pre3 24 Sep 2020 M1 Apache-2.0 Yes Details →
2.0-pre2 08 Sep 2020 M1 Apache-2.0 Yes Details →

All 42 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.graphhopper:graphhopper-nav

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.graphhopper:graphhopper-nav

Is com.graphhopper:graphhopper-nav safe to use?

Vulert records 1 vulnerabilities for com.graphhopper:graphhopper-nav in Maven: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.graphhopper:graphhopper-nav's Vulert package health score?

Vulert scores com.graphhopper:graphhopper-nav 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of com.graphhopper:graphhopper-nav affected?

No. 12.0-pre2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of com.graphhopper:graphhopper-nav should I use?

12.0-pre2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.graphhopper:graphhopper-nav have?

1 vulnerability is recorded for com.graphhopper:graphhopper-nav in the Maven ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.graphhopper:graphhopper-nav vulnerabilities disclosed?

0 vulnerabilities were recorded for com.graphhopper:graphhopper-nav in the last 12 months, and the oldest entry in this database dates to 19 May 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.graphhopper:graphhopper-nav are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.graphhopper:graphhopper-nav for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.graphhopper:graphhopper-nav version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.