CVE-2025-59340: Jinjava Jinjava Has Sandbox Bypass Vulnerability
CRITICALCVE-2025-59340 is a CRITICAL (CVSS 9.8) jinjava has sandbox bypass vulnerability (CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine) affecting Jinjava libraries in the Maven ecosystem. The issue involves jinjava has sandbox bypass via javatype-based deserialization. Remediation is available by upgrading affected packages to version 2.8.1, 2.7.5.
CVE-2025-59340 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2025-59340
To remediate this vulnerability, upgrade all affected Jinjava dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>com.hubspot.jinjava</groupId>
<artifactId>jinjava</artifactId>
<version>2.8.1</version>
</dependency>
<dependency>
<groupId>com.hubspot.jinjava</groupId>
<artifactId>jinjava</artifactId>
<version>2.7.5</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=com.hubspot.jinjava
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2025-59340, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=com.hubspot.jinjava
Analyze the terminal output to locate any version of Jinjava in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.1), your application is affected.
Note: The mvn dependency:tree -Dincludes=com.hubspot.jinjava command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine, where 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. In Jinjava, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-59340 Affected Jinjava Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
com.hubspot.jinjava:jinjava
|
Maven |
≥ 2.8.0
< 2.8.1
All 1 versions
2.8.0
|
2.8.1
|
|
com.hubspot.jinjava:jinjava
|
Maven |
≥ 2.7.0
< 2.7.5
|
2.7.5
|
References
Frequently Asked Questions
What is CVE-2025-59340?
Which Jinjava versions are affected?
What version fixes CVE-2025-59340?
Is jinjava affected?
What is the CVSS score of CVE-2025-59340?
What CWE is associated with CVE-2025-59340?
How can I check Maven dependencies for CVE-2025-59340?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m49c-g9wr-hv6v",
"modified" : "2026-07-31T22:15:57Z",
"published" : "2025-09-17T19:56:21Z",
"aliases" : [ "CVE-2025-59340" ],
"summary" : "jinjava has Sandbox Bypass via JavaType-Based Deserialization",
"details" : "### Summary\n\njinjava’s current sandbox restrictions prevent direct access to dangerous methods such as `getClass()`, and block instantiation of Class objects. However, these protections can be bypassed.\n\nBy using mapper.getTypeFactory().constructFromCanonical(), it is possible to instruct the underlying ObjectMapper to deserialize attacker-controlled input into arbitrary classes. This enables the creation of semi-arbitrary class instances without directly invoking restricted methods or class literals.\n\nAs a result, an attacker can escape the sandbox and instantiate classes such as java.net.URL, opening up the ability to access local files and URLs(e.g., file:///etc/passwd). With further chaining, this primitive can potentially lead to remote code execution (RCE).\n\n### Details\n\njinjava templates expose a built-in variable `____int3rpr3t3r____`, which provides direct access to the jinjavaInterpreter instance.\nThis variable was previously abused and protections were added to prevent call method from `JinjavaInterpreter` instances (see [Add interpreter to blacklist](https://github.com/HubSpot/jinjava/commit/1b9aaa4b420c58b4a301cf4b7d26207f1c8d1165)).\nHowever, interacting with the properties of `JinjavaInterpreter` instances remains [unrestricted](https://github.com/HubSpot/jinjava/blob/jinjava-2.8.0/src/main/java/com/hubspot/jinjava/el/ext/JinjavaBeanELResolver.java#L80-L84).\n\nFrom `____int3rpr3t3r____`, it is possible to traverse to the `config` field, which exposes an ObjectMapper. By invoking `readValue(String content, JavaType valueType)` on this ObjectMapper, an attacker can instantiate arbitrary classes specified via `JavaType`.\n\nAlthough jinjava explicitly restricts dangerous classes such as `Class`, `ClassLoader`, and so on inside `JinjavaBeanELResolver`, the `JavaType` class itself is [not restricted](https://github.com/HubSpot/jinjava/blob/jinjava-2.8.0/src/main/java/com/hubspot/jinjava/el/ext/JinjavaBeanELResolver.java#L246-L262). \n\nAs a result, an attacker can leverage `JavaType` construction (`constructFromCanonical`) to instantiate semi-arbitrary classes without directly calling restricted methods.\n\nThis allows sandbox escape and the creation of powerful primitives. \n\n### Impact\nEscape the Jinjava sandbox and instantiate a wide range of classes using JavaType.\nThis capability can be used to read arbitrary files and to perform full read SSRF by creating network-related objects.\nIn certain environments, depending on the available classes, this primitive can even lead to complete remote code execution.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "com.hubspot.jinjava:jinjava"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.8.0"
}, {
"fixed" : "2.8.1"
} ]
} ],
"versions" : [ "2.8.0" ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "com.hubspot.jinjava:jinjava"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.7.0"
}, {
"fixed" : "2.7.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/HubSpot/jinjava/security/advisories/GHSA-m49c-g9wr-hv6v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-59340"
}, {
"type" : "WEB",
"url" : "https://github.com/github/advisory-database/pull/8141"
}, {
"type" : "WEB",
"url" : "https://github.com/HubSpot/jinjava/commit/66df351e7e8ad71ca04dcacb4b65782af820b8b1"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/HubSpot/jinjava"
}, {
"type" : "WEB",
"url" : "https://github.com/HubSpot/jinjava/releases/tag/jinjava-2.7.5"
}, {
"type" : "WEB",
"url" : "https://github.com/HubSpot/jinjava/releases/tag/jinjava-2.8.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1336" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2025-09-17T19:56:21Z",
"nvd_published_at" : "2025-09-17T20:15:36Z"
}
}