Quick answers
- Is CVE-2026-82806 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82806 being exploited in the wild.
- How severe is CVE-2026-82806?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Apache APISIX 2.3.0 before 3.7.0.
- Is there a fix for CVE-2026-82806?
- Yes: fixed in 3.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82806 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82806?
- Check whether you run Apache APISIX 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: 3.7.0
Technical details
A data element exposure vulnerability exists in APISIX's authz-keycloak plugin where authorization scope information persists across requests on the same route due to mutable static permission list mutation. An authenticated user (PR:L) making requests to an affected APISIX instance can trigger the vulnerability, which causes scope data from one request to affect authorization decisions in subsequent requests on the same route, leading to scope expansion. The fix is available in version 3.7.0.
Affected products
- Apache APISIX 2.3.0 before 3.7.0
Timeline
- 2026-10-01: disclosed