CVE-2026-82955
Hard-coded disable of TLS for JWKS in aeriOS KrakenD allows token validation bypass.
Is CVE-2026-82955 being exploited?
Not confirmed. CVE-2026-82955 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-82955?
CVE-2026-82955 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82955?
Yes. A fix has been recorded for CVE-2026-82955. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82955 affect?
CVE-2026-82955 affects Eclipse aeriOS API Gateway (development builds), Bundled KrakenD instance in aeriOS, Helm deployments using aeriOS api-gateway (dev). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82955?
Upgrade to patched commit or set krakend.config.disableJwkSecurity=false in Helm.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM of JWKS fetch can supply malicious keys to bypass token validation, enabling impersonation and unauthorized access, possibly leading to privilege escalation.
Immediate action required
- affected>= 371ea2101e42aa6503161ce08bbe986e319a9c2f and < e680c69c34b82db4944517198330cc447a1e8f98
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.