← Back
CVE-2025-59340
Vulnerability in com.hubspot.jinjava:jinjava (CVE-2025-59340)
Summary
vulnerability in com.hubspot.jinjava:jinjava (CVE-2025-59340). Risk of unauthorized operations or information disclosure. Exploitable via ``____int3rpr3t3r____``. Mitigation: upgrade to `2.7.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-59340** has been found in com.hubspot.jinjava:jinjava.
Attackers can target a specific entry point like ``____int3rpr3t3r____`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade com.hubspot.jinjava:jinjava to **2.7.5** or later.
If unsure, ask your IT team or search "com.hubspot.jinjava:jinjava CVE-2025-59340" on the vendor's site.
CVE-2025-59340 (com.hubspot.jinjava:jinjava) — CWE-1336 /
Attack surface: `____int3rpr3t3r____` / `JinjavaInterpreter` / `config` / `JavaType`
Patched: `2.7.5` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-1336) exists in com.hubspot.jinjava:jinjava. Attackers reach the vulnerable code path via ``____int3rpr3t3r____`` without authentication.
📍 Affected scope
com.hubspot.jinjava:jinjava — . Attack surface: `____int3rpr3t3r____` / `JinjavaInterpreter` / `config` / `JavaType`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.7.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'com.hubspot.jinjava:jinjava' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'com.hubspot.jinjava:jinjava' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.hubspot.jinjava:jinjava` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade com.hubspot.jinjava:jinjava to 2.7.5ステージング環境で 2.7.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
com.hubspot.jinjava:jinjava
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.5"}]}]
References
- web https://github.com/HubSpot/jinjava/security/advisories/GHSA-m49c-g9wr-hv6v
- web https://github.com/HubSpot/jinjava/commit/66df351e7e8ad71ca04dcacb4b65782af820b8b1
- web https://github.com/HubSpot/jinjava/releases/tag/jinjava-2.8.1
- web https://nvd.nist.gov/vuln/detail/CVE-2025-59340
- web https://github.com/HubSpot/jinjava/releases/tag/jinjava-2.7.5
- web https://github.com/github/advisory-database/pull/8141
- web https://github.com/advisories/GHSA-m49c-g9wr-hv6v