CVE-2026-25526: JinJava Bypass through ForTag leads to Arbitrary Java Execution

CVE-2026-25526 · Severity: low · CVSS 3.1 · Published 2026-02-03

JinJava Bypass through ForTag leads to Arbitrary Java Execution

Technologies: com.hubspot.jinjava:jinjava (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-25526 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-25526 being exploited in the wild.
How severe is CVE-2026-25526?
Low severity, with a CVSS score of 3.1, published 3 February 2026.
Which products and versions are affected?
com.hubspot.jinjava:jinjava (Maven) ECOSYSTEM:introduced=2.8.0,fixed=2.8.3.
Is there a fix for CVE-2026-25526?
Yes. com.hubspot.jinjava:jinjava (Maven): upgrade to 2.8.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-25526?
Check whether you run com.hubspot.jinjava:jinjava (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.hubspot.jinjava:jinjava (Maven): upgrade to 2.8.3 or later
    # set com.hubspot.jinjava:jinjava to 2.8.3 in your pom.xml or build.gradle

Affected products

  • com.hubspot.jinjava:jinjava (Maven) ECOSYSTEM:introduced=2.8.0,fixed=2.8.3

Identifiers

  • CVE-2026-25526
  • GHSA-gjx9-j8f8-7j74

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.