Skip to main content
VulnerabilityPublished

CVE-2026-25526: HubSpot jinjava · Template Injection

Affects HubSpot jinjavaSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.8.3 or 2.7.6 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.3, 2.7.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade jinjava and com.hubspot/jinjava to 2.8.3 or 2.7.6.

Affected software

ProductAffectedFixed in
HubSpotjinjavaAffected
  • <2.8.3
Fixed in
  • 2.8.3
HubSpotjinjavaAffected
  • <2.7.6
Fixed in
  • 2.7.6
Mavencom.hubspot/jinjavapkg:maven/com.hubspot/jinjavaOther threatsAffected
  • <2.7.6
  • <2.8.3
Fixed in
  • 2.7.6
  • 2.8.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade JinJava to version 2.7.6 or 2.8.3 immediately to apply the official patches that fix the sandbox bypass vulnerability.
  2. 3. Review and audit template files for unsafe usage of ForTag or other constructs that could be exploited, removing or refactoring risky templates. 4. Implement strict input validation and sanitization on any user-supplied data that is rendered via JinJava templates to reduce injection risks. 5. Employ runtime security controls such as Java Security Manager policies or containerization to limit the impact of potential code execution. 6. Monitor logs and network traffic for anomalous template rendering requests or unexpected Java class instantiations. 7. Establish incident response plans specific to template engine exploitation scenarios. 8. Engage with HubSpot support or security advisories for any additional guidance or updates.

Description

CVE-2026-25526 is a critical vulnerability in HubSpot's JinJava template engine versions prior to 2.7.6 and 2.8.3. It allows unauthenticated remote attackers to execute arbitrary Java code by bypassing sandbox restrictions through the ForTag template construct. This leads to full compromise of confidentiality, integrity, and availability of affected systems without requiring user interaction. The vulnerability arises from improper neutralization of special elements used in the template engine (CWE-1336). Although no known exploits are currently in the wild, the high CVSS score of 9.8 indicates a severe risk.

References

Community reviews

Loading reviews…