Cyber Resilience

CVE-2026-25526

Hubspot Jinjava ≤ 2.7.6

Published
04 February 2026
Modified
20 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0089 56th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2026-25526 is a critical-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Hubspot Jinjava. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-25526 is a critical vulnerability in JinJava, a Java-based template engine that adapts Django template syntax for rendering Jinja templates. Prior to versions 2.7.6 and 2.8.3, the ForTag implementation allows attackers to bypass built-in sandbox restrictions, enabling arbitrary Java class instantiation and file access. This flaw, classified under CWE-1336 (Improvable Restriction of Excessive Authentication Attempts, though contextually related to sandbox escape), carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating severe impact potential.

The vulnerability can be exploited remotely by unauthenticated attackers with no user interaction required, due to its network-accessible and low-complexity nature. Successful exploitation grants arbitrary Java code execution within the application's context, allowing attackers to instantiate any Java class and perform unrestricted file operations, effectively defeating JinJava's sandbox protections. This could lead to full system compromise, data exfiltration, or persistence on affected servers processing untrusted templates.

Mitigation is available through upgrading to JinJava versions 2.7.6 or 2.8.3, where the issue has been patched via specific commits (3d02e504d8bbb13bf3fe019e9ca7b51dfce7a998 and c7328dce6030ac718f88974196035edafef24441). The HubSpot security advisory (GHSA-gjx9-j8f8-7j74) and release notes detail these fixes, recommending immediate updates for all deployments using vulnerable versions.

EU & UK References

Vulnerability Data

JinJava is a Java-based template engine based on django template syntax, adapted to render jinja templates. Prior to versions 2.7.6 and 2.8.3, JinJava is vulnerable to arbitrary Java execution via bypass through ForTag. This allows arbitrary Java class instantiation and…

more

file access bypassing built-in sandbox restrictions. This issue has been patched in versions 2.7.6 and 2.8.3.

CWE(s)
CWE-1336

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59340Same product: Hubspot Jinjava
CVE-2025-64087Shared CWE-1336
CVE-2026-44916Shared CWE-1336
CVE-2025-49136Shared CWE-1336
CVE-2025-32461Shared CWE-1336
CVE-2024-8238Shared CWE-1336
CVE-2025-57811Shared CWE-1336
CVE-2025-12107Shared CWE-1336
CVE-2026-42252Shared CWE-1336
CVE-2025-14700Shared CWE-1336

Affected Assets

hubspot
jinjava
≤ 2.7.6 · 2.8.0 — 2.8.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis can discover missing neutralization of template directives.

SI-10 Information Input Validation good match

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of safe templating APIs and proper escaping of external input.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References