{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18674 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18674 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18674 is a high-severity missing authorization vulnerability in Kong Mesh, published on 17 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18674 and fix it if it is affected.\n\nWhat it is: CVE-2026-18674 is a high-severity missing authorization vulnerability in Kong Mesh, published on 17 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18674 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-18674/ (Markdown: https://insights.sbomify.com/CVE-2026-18674/index.md)","id":"CVE-2026-18674","markdown":"https://insights.sbomify.com/CVE-2026-18674/index.md","name":"CVE-2026-18674","record":{"aliases":["GHSA-fxcr-qwx6-5h7q","GHSA-m58j-fjmc-h3g4"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kong Mesh control plane","requires_auth":"high_privilege","summary":"Authenticated zones can bypass cross-zone isolation to inject or overwrite resources in other zones' namespaces on the Kong Mesh global control plane.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Kong","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone.\n\nThe result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide.\n\nThe root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.","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":"Missing authorization in Kong Mesh","id":"CVE-2026-18674","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Kong Mesh: control plane denial of service via a malformed dataplane token with a non-string JWT kid","id":"CVE-2026-18675"},"packages":[],"prev":{"headline":"Kong Mesh: the kuma-dp readiness service exposes the Envoy admin API without authentication","id":"CVE-2026-18673"},"products":["Kong Mesh"],"published":"2026-08-17","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-17","vendors":["Kong Inc."]},"summary":"Authenticated zones can bypass cross-zone isolation to inject or overwrite resources in other zones' namespaces on the Kong Mesh global control plane.","url":"https://insights.sbomify.com/CVE-2026-18674/"}