Code Injection in flink (CVE-2026-35194)
Summary
Code injection in flink (CVE-2026-35194). Confidential information can be exposed externally. Mitigation: upgrade to 1.20.4, 2.0.2, 2.1.1, 2.2.1 or later.
Original description
The description as published by the source.
Code injection in SQL code generation in Apache Flink 1.15.0 through 1.20.x and 2.0.0 through 2.x allows authenticated users with query submission privileges to execute arbitrary code on TaskManagers via maliciously crafted SQL queries. The vulnerability affects JSON functions (1.15.0+) and LIKE expressions with ESCAPE clauses (1.17.0+). User-controlled strings are interpolated into generated Java code without proper escaping, allowing attackers to break out of string literals and inject arbitrary expressions.
Users are recommended to upgrade to either version 1.20.4, 2.0.2, 2.1.2 or 2.2.1, which fixes this issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35194 has been found in flink.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade flink to 1.20.4, 2.0.2, 2.1.1, 2.2.1 or later.
If unsure, ask your IT team or search "flink CVE-2026-35194" on the vendor's site.
CVE-2026-35194 (flink) — CWE-94 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.20.4, 2.0.2, 2.1.1, 2.2.1 — 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.
Arbitrary code execution (CWE-94) exists in flink.
Check the vendor advisory for the affected versions of flink.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 1.20.4, 2.0.2, 2.1.1, 2.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flink' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flink' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flinkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flink to 1.20.4, 2.0.2, 2.1.1, 2.2.1ステージング環境で 1.20.4, 2.0.2, 2.1.1, 2.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory openwall.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com