{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18675 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18675 is a medium-severity denial of service vulnerability in Kong Mesh, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18675 and fix it if it is affected.\n\nWhat it is: CVE-2026-18675 is a medium-severity denial of service vulnerability in Kong Mesh, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18675 in the wild and no public exploit code.\n\nAffected product: Kong Mesh. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-18675/ (Markdown: https://insights.sbomify.com/CVE-2026-18675/index.md)","id":"CVE-2026-18675","markdown":"https://insights.sbomify.com/CVE-2026-18675/index.md","name":"CVE-2026-18675","record":{"aliases":["GHSA-5mxq-7xq4-3vx8","GHSA-7gh2-244h-962w"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kong Mesh control plane","requires_auth":"none","summary":"Unauthenticated attackers can crash the Kong Mesh control plane by sending a malformed dataplane token with a non-string JWT kid, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Kong","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"},{"id":"CWE-248","name":"Uncaught Exception"}],"description":"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.\n\nThe 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\n\nA single request is a transient interruption; sustaining an outage requires repeated requests.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Kong Mesh: control plane denial of service via a malformed dataplane token with a non-string JWT kid","id":"CVE-2026-18675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Kong Mesh: default control plane config leaks the admin token cross-origin via a CORS wildcard and localhost admin","id":"CVE-2026-18676"},"packages":[],"prev":{"headline":"Missing authorization in Kong Mesh","id":"CVE-2026-18674"},"products":["Kong Mesh"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Kong Inc."]},"summary":"Unauthenticated attackers can crash the Kong Mesh control plane by sending a malformed dataplane token with a non-string JWT kid, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-18675/"}