dbcve.org
JinjavaApplication · Hubspot

CVE-2026-25526

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 2.7.6 / 2.8.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 file access bypassing built-in sandbox restrictions. This issue has been patched in versions 2.7.6 and 2.8.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JinJava template engine contains a sandbox bypass vulnerability in the ForTag (for loop) implementation that allows attackers to instantiate arbitrary Java classes and access files, achieving remote code execution. The vulnerability bypasses built-in sandbox restrictions designed to prevent dangerous operations.

MitigationUpgrade JinJava to version 2.7.6 or 2.8.3 or later to patch the sandbox bypass. If immediate upgrade is not possible, review and restrict template input sources to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JinjavaApplication
Affected:< 2.7.6>= 2.8.0, < 2.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JinJava version
    Locate the JinJava library in your project dependencies (e.g., pom.xml, build.gradle, or JAR manifest) and note the exact version number
    Affected if Version is below 2.7.6, or is 2.8.0, 2.8.1, or 2.8.2
  2. Confirm ForTag usage in templates
    Search your template files (.html, .java, or custom template directories) for occurrences of the 'for' tag syntax (e.g., {% for item in collection %}) used by JinJava
    Affected if Templates utilize the ForTag to iterate over collections
  3. Verify sandbox mode is intended
    Check your JinJava configuration for sandbox enforcement (look for JinjavaConfig or SandboxSecurityPolicy initialization in your codebase)
    Affected if Sandbox mode is enabled but ForTag can still be processed with user-supplied template input
  4. Assess template input source
    Determine whether templates are compiled from external/untrusted sources (user uploads, API inputs, remote content) versus trusted internal sources only
    Affected if Templates are sourced from untrusted or user-controlled input without sanitization

Your environment is affected if JinJava version is below 2.7.6 or between 2.8.0-2.8.2, ForTag is used in your templates, and templates are processed from external/untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.6 / 2.8.3 or later
Fixed in 2.7.62.8.3
Vendor patch github.com →
Interim mitigation

Upgrade JinJava to version 2.7.6 or 2.8.3 or later to patch the sandbox bypass. If immediate upgrade is not possible, review and restrict template input sources to trusted users only.

Recommended fix High confidence

JinJava 2.7.6 or 2.8.3 (choose the appropriate version based on your current minor branch)

  1. 1. Identify the current JinJava version in use by checking your project's dependency file (e.g., pom.xml, build.gradle, or package manager)
  2. 2. If using a version < 2.7.6 or >= 2.8.0 but < 2.8.3, plan an upgrade
  3. 3. Upgrade JinJava to version 2.7.6 or 2.8.3 (or the latest available version in your minor branch)
  4. 4. Rebuild and redeploy the application with the updated dependency
  5. 5. Test that template rendering functionality still works as expected
  6. 6. Verify the fix by confirming the new version is loaded at runtime
Caveat Review JinJava release notes for your target version to check for any breaking changes or deprecations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jinjava Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25526 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data