VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.hubspot.jinjava:jinjava: vulnerability history, versions and safety

com.hubspot.jinjava:jinjava is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 97 releases, from Jan 2019 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 03 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.hubspot.jinjava:jinjava vulnerabilities

Vulert verdict on com.hubspot.jinjava:jinjava 2.8.4 i

Updated on 23 Oct 2026

Good news: 2.8.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 2.8.4 — unaffected i
  • Vulnerabilities on record 4 over 7 years · 1 in the last year i
  • Latest disclosure 03 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 12 packages i
  • Last release 2 months ago 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.hubspot.jinjava:jinjava, 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
2.8.4 24 Jul 2026 none Apache-2.0 — Details →
2.7.6 02 Feb 2026 C1 Apache-2.0 Yes Details →
2.8.3 02 Feb 2026 none Apache-2.0 — Details →
2.8.2 22 Oct 2025 C1 Apache-2.0 Yes Details →
2.7.5 29 Sep 2025 C1 Apache-2.0 Yes Details →
2.8.1 16 Sep 2025 C1 Apache-2.0 Yes Details →
2.8.0 12 May 2025 C2 — Yes Details →
2.7.4 06 Dec 2024 C1 — Yes Details →
2.7.3 12 Sep 2024 C1 — Yes Details →
2.7.2 14 Feb 2024 C1 — Yes Details →
2.7.1 11 Aug 2023 C1 — Yes Details →
2.7.0 06 Mar 2023 C1 — Yes Details →
2.6.0 29 Oct 2021 C1 — Yes Details →
2.5.10 03 Sep 2021 C1 — Yes Details →
2.5.9 20 May 2021 C1 — Yes Details →
2.5.8 20 May 2021 C1 — Yes Details →
2.5.7 09 Apr 2021 C1 — Yes Details →
2.5.6 07 Oct 2020 C1 — Yes Details →
2.5.5 23 Jun 2020 C1 — Yes Details →
2.5.4 04 May 2020 C1 — Yes Details →
2.5.3 06 Mar 2020 C1 M1 — Yes Details →
2.5.2 11 Jul 2019 C1 M1 — Yes Details →
2.5.1 07 Jun 2019 C1 M1 — Yes Details →
2.5.0 11 Mar 2019 C1 M1 — Yes Details →
2.4.15 05 Feb 2019 C1 M1 — Yes Details →
2.4.14 08 Jan 2019 C1 M1 — Yes Details →
2.4.13 07 Jan 2019 C1 M1 — Yes Details →
2.4.12 21 Nov 2018 C1 M1 — Yes Details →
2.4.11 23 Oct 2018 C1 M1 — Yes Details →
2.4.10 20 Oct 2018 C1 M1 — Yes Details →
2.4.9 15 Oct 2018 C1 M1 — Yes Details →
2.4.8 07 Sep 2018 C1 M1 — Yes Details →
2.4.7 31 Aug 2018 C1 M1 — Yes Details →
2.4.6 29 Aug 2018 C1 M1 — Yes Details →
2.4.5 16 Aug 2018 C1 M2 — Yes Details →
2.4.4 10 Jul 2018 C1 M2 — Yes Details →
2.4.3 13 Jun 2018 C1 M2 — Yes Details →
2.4.2 02 Jun 2018 C1 M2 — Yes Details →
2.4.1 22 Apr 2018 C1 M2 — Yes Details →
2.4.0 28 Feb 2018 C1 M2 — Yes Details →
2.3.6 09 Feb 2018 C1 M2 — Yes Details →
2.3.5 26 Jan 2018 C1 M2 — Yes Details →
2.3.4 30 Nov 2017 C1 M2 — Yes Details →
2.3.3 17 Nov 2017 C1 M2 — Yes Details →
2.3.1 14 Nov 2017 C1 M2 — Yes Details →
2.3.0 30 Oct 2017 C1 M2 — Yes Details →
2.2.10 25 Oct 2017 C1 M2 — Yes Details →
2.2.9 31 Aug 2017 C1 M2 — Yes Details →
2.2.8 21 Aug 2017 C1 M2 — Yes Details →
2.2.7 13 Aug 2017 C1 M2 — Yes Details →
2.2.6 03 Aug 2017 C1 M2 — Yes Details →
2.2.5 02 Aug 2017 C1 M2 — Yes Details →
2.2.4 01 Aug 2017 C1 M2 — Yes Details →
2.2.3 21 Jul 2017 C1 M2 — Yes Details →
2.2.2 19 Jul 2017 C1 M2 — Yes Details →
2.2.1 14 Jun 2017 C1 M2 — Yes Details →
2.2.0 12 May 2017 C1 M2 — Yes Details →
2.1.19 12 Apr 2017 C1 M2 — Yes Details →
2.1.18 10 Apr 2017 C1 M2 — Yes Details →
2.1.17 31 Mar 2017 C1 M2 — Yes Details →
2.1.16 09 Mar 2017 C1 M2 — Yes Details →
2.1.15 18 Jan 2017 C1 M2 — Yes Details →
2.1.14 18 Nov 2016 C1 M2 — Yes Details →
2.1.13 02 Nov 2016 C1 M2 — Yes Details →
2.1.12 13 Oct 2016 C1 M2 — Yes Details →
2.1.11 19 Jul 2016 C1 M2 — Yes Details →
2.1.10 07 Jul 2016 C1 M2 — Yes Details →
2.1.9 19 May 2016 C1 M2 — Yes Details →
2.1.8 28 Apr 2016 C1 M2 — Yes Details →
2.1.7 21 Mar 2016 C1 M2 — Yes Details →
2.1.6 25 Feb 2016 C1 M2 — Yes Details →
2.1.5 17 Feb 2016 C1 M2 — Yes Details →
2.1.4 11 Feb 2016 C1 M2 — Yes Details →
2.1.3 29 Jan 2016 C1 M2 — Yes Details →
2.1.2 18 Dec 2015 C1 M2 — Yes Details →
2.1.1 01 Dec 2015 C1 M2 — Yes Details →
2.1.0 20 Oct 2015 C1 M2 — Yes Details →
2.0.10 21 Sep 2015 C1 M2 — Yes Details →
2.0.11-java7 20 Sep 2015 C1 M2 — Yes Details →
2.0.9 28 Aug 2015 C1 M2 — Yes Details →
2.0.8 29 Jul 2015 C1 M2 — Yes Details →
2.0.7 16 Jul 2015 C1 M2 — Yes Details →
2.0.6 24 Jun 2015 C1 M2 — Yes Details →
2.0.5 27 May 2015 C1 M2 Apache-2.0 Yes Details →
2.0.4 13 May 2015 C1 M2 Apache-2.0 Yes Details →
2.0.3 07 May 2015 C1 M2 Apache-2.0 Yes Details →
2.0.2 27 Apr 2015 C1 M2 Apache-2.0 Yes Details →
2.0.1 10 Apr 2015 C1 M2 Apache-2.0 Yes Details →
2.0.0 11 Mar 2015 C1 M2 Apache-2.0 Yes Details →
1.0.9 03 Mar 2015 C1 M2 Apache-2.0 Yes Details →
1.0.8 20 Jan 2015 C1 M2 Apache-2.0 Yes Details →
1.0.7 19 Jan 2015 C1 M2 Apache-2.0 Yes Details →
1.0.6 06 Jan 2015 C1 M2 Apache-2.0 Yes Details →
1.0.5 19 Dec 2014 C1 M2 Apache-2.0 Yes Details →
1.0.4 17 Dec 2014 C1 M2 Apache-2.0 Yes Details →
1.0.3 25 Nov 2014 C1 M2 Apache-2.0 Yes Details →
1.0.2 30 Oct 2014 C1 M2 Apache-2.0 Yes Details →
1.0.1 24 Oct 2014 C1 M2 Apache-2.0 Yes Details →
1.0.0 14 Oct 2014 C1 M2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 1
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.hubspot.jinjava:jinjava

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2025-59340: Sandbox Bypass in com.hubspot.jinjava:jinjava Allows Arbitrary Class Instantiation 9.8 critical 2.8.1 17 Sep 2025
Critical Sandbox Bypass Vulnerability in Jinjava Allows Arbitrary Java Execution 9.8 critical 2.8.3 03 Feb 2026
CVE-2020-12668: Unauthorized access to Class instance in Jinjava 6.5 medium 2.5.4 09 Feb 2022
CVE-2018-18893: Jinjava getClass Method Vulnerability 5.3 medium 2.4.6 04 Jan 2019

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.hubspot.jinjava:jinjava

Is com.hubspot.jinjava:jinjava safe to use?

Vulert records 4 vulnerabilities for com.hubspot.jinjava:jinjava in Maven: 2 critical, 0 high, 2 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.hubspot.jinjava:jinjava's Vulert package health score?

Vulert scores com.hubspot.jinjava:jinjava 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.hubspot.jinjava:jinjava affected?

No. 2.8.4, 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.hubspot.jinjava:jinjava should I use?

2.8.4 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.hubspot.jinjava:jinjava have?

4 vulnerabilities are recorded for com.hubspot.jinjava:jinjava in the Maven ecosystem: 2 critical, 0 high, 2 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.hubspot.jinjava:jinjava vulnerabilities disclosed?

1 vulnerability was recorded for com.hubspot.jinjava:jinjava in the last 12 months, and the oldest entry in this database dates to 04 Jan 2019. 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.hubspot.jinjava:jinjava 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.hubspot.jinjava:jinjava for upcoming vulnerabilities?

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