Vulnerability in org.apache.fluss:fluss-common (CVE-2026-49361)
Summary
Vulnerability in org.apache.fluss:fluss-common (CVE-2026-49361). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.9.1-incubating or later.
Original description
The description as published by the source.
Apache Fluss versions prior to 0.9.1 configure the Netty LengthFieldBasedFrameDecoder with Integer.MAX_VALUE as the maximum frame length, allowing unauthenticated remote attackers to exhaust JVM heap memory on TabletServer and CoordinatorServer by sending specially crafted frame headers, resulting in denial of service.
This issue affects Apache Fluss (incubating): 0.8.0 and 0.9.0.
Users are recommended to upgrade to version 0.9.1, which fixes the issue.
Source: GitHub Security Advisories (Global) 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-49361 has been found in org.apache.fluss:fluss-common.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.apache.fluss:fluss-common to 0.9.1-incubating or later.
If unsure, ask your IT team or search "org.apache.fluss:fluss-common CVE-2026-49361" on the vendor's site.
CVE-2026-49361 (org.apache.fluss:fluss-common) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.9.1-incubating — 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.
A vulnerability (CWE-400) exists in org.apache.fluss:fluss-common.
Check the vendor advisory for the affected versions of org.apache.fluss:fluss-common.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.9.1-incubating.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.apache.fluss:fluss-common を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.fluss:fluss-common to 0.9.1-incubatingステージング環境で 0.9.1-incubating に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory lists.apache.org
- advisory github.com
- package github.com
- web github.com
- web openwall.com
- web github.com