Deploy autonomous AI agents that reason, exploit, and validate complex vulnerability chains — not another scanner, an agentic system that thinks like a senior pentester.
CVE-2026-25526 is a critical severity vulnerability with a CVSS score of 9.8. Exploits are available; patches have been released and should be applied urgently.
Very low probability of exploitation
EPSS predicts the probability of exploitation in the next 30 days based on real-world threat data, complementing CVSS severity scores with actual risk assessment.
Vulnerability Type: Sandbox Bypass / Remote Code Execution
Affected Component: Jinjava
Affected Users:
Severity: Critical - allows arbitrary Java class instantiation and file access bypassing built-in sandbox restrictions
Root Cause: Multiple security bypass vulnerabilities in Jinjava's sandbox mechanism:
ForTag Property Access Bypass: The ForTag class does not enforce JinjavaBeanELResolver restrictions when iterating over object properties using Introspector.getBeanInfo() and invoking getter methods via PropertyDescriptor.getReadMethod()
Restricted Class Instantiation: The sandbox's type allowlist can be bypassed by using ObjectMapper to instantiate classes through JSON deserialization, including creating new JinjavaELContext and JinjavaConfig instances
Attack Vector: An attacker with the ability to create or edit Jinja templates can:
ObjectMapper to enable default typing/etc/passwd)Status: Patched - CVE-2026-25526
Users should upgrade to one of the following versions which contain fixes for this vulnerability:
| Vendor | Product |
|---|---|
| Hubspot | Jinjava |
Please cite this page when referencing data from Strobes VI. Proper attribution helps support our vulnerability intelligence research.
Fix Components:
ForTag Security Hardening
ForTag.renderForCollection() to enforce JinjavaBeanELResolver restrictionsEnhanced Type Validation
JinjavaBeanELResolver.isRestrictedClass() to prevent instantiation of sensitive typesConfiguration Protection
JinjavaConfig or JinjavaELContext instances via ObjectMapperreadOnlyResolver configuration from untrusted templatesCollection Type Validation
HubLELResolver to prevent collection type wrapping bypassesObjectMapper Restrictions
ObjectMapper.enableDefaultTyping() to prevent enabling via less restrictive ELResolverInformation for Users: Upgrade to version 2.8.3 or 2.7.6 or later to address this vulnerability.