Quick answers
- Is CVE-2026-97720 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97720 being exploited in the wild.
- How severe is CVE-2026-97720?
- Informational severity, published 7 October 2026.
- Which products and versions are affected?
- Apache Impala up to and including 4.5.2.
- Is there a fix for CVE-2026-97720?
- Yes: fixed in 4.5.3. Until then: Disable JWT/OAuth authentication for Impala executors until upgrading to version 4.5.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97720 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-97720?
- Check whether you run Apache Impala at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.5.3
Disable JWT/OAuth authentication for Impala executors until upgrading to version 4.5.3 or later.
Technical details
The vulnerability stems from incorrect JWT/OAuth implementation in Impala executors' webserver that does not validate Bearer token signatures. An attacker can craft a forged JWT token and gain unauthorized access to resources served by the executor webserver when JWT/OAuth authentication is enabled. No authentication bypass patch is required; users can disable JWT/OAuth auth as a mitigation or upgrade to the fixed version.
Affected products
- Apache Impala up to and including 4.5.2
Timeline
- 2026-10-07: disclosed