CVE-2026-25526
Arbitrary Java Execution via ForTag in JinJava Template Engine
Publication date: 2026-02-04
Last updated on: 2026-02-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hubspot | jinjava | to 2.7.6 (exc) |
| hubspot | jinjava | From 2.8.0 (inc) to 2.8.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1336 | The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects JinJava, a Java-based template engine that uses django template syntax to render jinja templates. Prior to versions 2.7.6 and 2.8.3, an attacker could exploit a bypass through the ForTag feature to execute arbitrary Java code. This means the attacker can instantiate any Java class and access files, circumventing the built-in sandbox restrictions designed to prevent such actions.
How can this vulnerability impact me? :
The vulnerability allows an attacker to execute arbitrary Java code remotely without any privileges or user interaction. This can lead to complete compromise of the affected system, including unauthorized access to sensitive files, data manipulation, and disruption of service. The CVSS score of 9.8 indicates a critical severity with high impact on confidentiality, integrity, and availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade JinJava to version 2.7.6 or 2.8.3 or later, where the issue has been patched.