cve.bz

CVE-2026-18675 kong inc. kong mesh: Uncaught Exception

5.3 mediumEPSS 0.6%

Medium (5.3) in kong inc. kong mesh. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
The dataplane token validator in kuma-cp performs an unchecked Go type assertion on the JWT kid header. A token whose kid is a JSON number decodes as a float64 and triggers a runtime panic before any signature, claims, or authorization check runs. The panic terminates the entire kuma-cp process, HTTP API, the health and readiness endpoints, and xDS. Unauthenticated access to the dataplane gRPC server can trigger the crash with a malformed token A single request is a transient interruption; sustaining an outage requires repeated requests.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-248 Uncaught Exception
CWE-704 Incorrect Type Conversion or Cast
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-18675 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18675?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18675?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18675 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Kong Inc. Kong Meshbefore 2.7.29
Kong Inc. Kong Meshfrom 2.8.0 before 2.9.19
Kong Inc. Kong Meshfrom 2.10.0 before 2.11.18
Kong Inc. Kong Meshfrom 2.12.0 before 2.12.14
Kong Inc. Kong Meshfrom 2.13.0 before 2.13.10
Kong Inc. Kong Meshfrom 2.14.0 before 2.14.2

References

Check your stackJSON