CVE-2026-18677 (GCVE-0-2026-18677)

Vulnerability from cvelistv5 – Published: 2026-08-12 18:47 – Updated: 2026-08-13 14:49
VLAI
Title
Kong Mesh: a dataplane token without a workload binding can claim any workload's SPIFFE identity
Summary
In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload's SPIFFE identity.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-08-13 14:49 UTC
CWE
  • CWE-290 - Authentication Bypass by Spoofing
Assigner
Kong CNA under the mitre root
CNA scorecard B 82/100 over 27 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Kong Inc. Kong Mesh Affected: 2.13.0 , < 2.13.10 (semver)
Affected: 2.14.0 , < 2.14.2 (semver)
guessed Create a notification for this product.
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-18677",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-13T14:49:14.103209Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-13T14:49:27.614Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "modules": [
            "kuma-cp"
          ],
          "platforms": [
            "Linux"
          ],
          "product": "Kong Mesh",
          "vendor": "Kong Inc.",
          "versions": [
            {
              "lessThan": "2.13.10",
              "status": "affected",
              "version": "2.13.0",
              "versionType": "semver"
            },
            {
              "lessThan": "2.14.2",
              "status": "affected",
              "version": "2.14.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eYou are affected if all of the following hold:\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe control plane runs in universal mode.\u003c/li\u003e\u003cli\u003eA \u003ccode\u003eMeshIdentity\u003c/code\u003e is configured whose SPIFFE ID path template derives from the workload label, including the default universal template \u003ccode\u003e/workload/{{ .Workload }}\u003c/code\u003e.\u003c/li\u003e\u003cli\u003eDataplanes authenticate with tokens that are not bound to a workload (tags-bound tokens, the common case, since workload binding is newer and optional).\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eYou are not affected if:\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe control plane runs in Kubernetes mode. Its identity template is \u003ccode\u003e/ns/{{ .Namespace }}/sa/{{ .ServiceAccount }}\u003c/code\u003e, and the control plane derives those values from the pod\u0027s real identity rather than from a label the workload sets.\u003c/li\u003e\u003cli\u003eYour \u003ccode\u003eMeshIdentity\u003c/code\u003e uses a SPIFFE template that does not reference the workload label.\u003c/li\u003e\u003cli\u003eEvery dataplane whose identity derives from the workload label already uses a workload-bound token.\u003c/li\u003e\u003c/ul\u003e"
            }
          ],
          "value": "You are affected if all of the following hold:\n\n  *  The control plane runs in universal mode.\n  *  A MeshIdentity is configured whose SPIFFE ID path template derives from the workload label, including the default universal template /workload/{{ .Workload }}.\n  *  Dataplanes authenticate with tokens that are not bound to a workload (tags-bound tokens, the common case, since workload binding is newer and optional).\n\n\n\n\nYou are not affected if:\n\n  *  The control plane runs in Kubernetes mode. Its identity template is /ns/{{ .Namespace }}/sa/{{ .ServiceAccount }}, and the control plane derives those values from the pod\u0027s real identity rather than from a label the workload sets.\n  *  Your MeshIdentity uses a SPIFFE template that does not reference the workload label.\n  *  Every dataplane whose identity derives from the workload label already uses a workload-bound token."
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "kanywst"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIn Kong Mesh running in universal mode with a \u003ccode\u003eMeshIdentity\u003c/code\u003e whose SPIFFE ID path template derives from the dataplane\u0027s \u003ccode\u003ekuma.io/workload\u003c/code\u003e label, the XDS authenticator in \u003ccode\u003ekuma-cp\u003c/code\u003e validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with \u003ccode\u003ekuma.io/workload\u003c/code\u003e set to any value and obtain another workload\u0027s SPIFFE identity.\u003c/p\u003e"
            }
          ],
          "value": "In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane\u0027s kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload\u0027s SPIFFE identity."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "Workload identity spoofing"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6,
            "baseSeverity": "MEDIUM",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-290",
              "description": "CWE-290 Authentication Bypass by Spoofing",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-12T18:47:06.710Z",
        "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "shortName": "Kong"
      },
      "references": [
        {
          "name": "Upstream advisory GHSA-744g-c785-x65q",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/kumahq/kuma/security/advisories/GHSA-744g-c785-x65q"
        },
        {
          "name": "kumahq/kuma#17474 (master)",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/kumahq/kuma/pull/17474"
        },
        {
          "name": "kumahq/kuma#17503 (release-2.13 backport)",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/kumahq/kuma/pull/17503"
        },
        {
          "name": "kumahq/kuma#17502 (release-2.14 backport)",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/kumahq/kuma/pull/17502"
        },
        {
          "name": "Kong MESH Changelog",
          "tags": [
            "release-notes"
          ],
          "url": "https://developer.konghq.com/mesh/changelog/"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eUpgrade to Kong Mesh 2.13.10 or 2.14.2, whichever matches your release line. In patched versions a dataplane whose identity derives from the \u003ccode\u003ekuma.io/workload\u003c/code\u003e label requires a workload-bound token; an unbound tags-only token is rejected at XDS authentication. Kubernetes mode and universal templates that do not reference the workload label keep working with unbound tokens.\u003c/p\u003e"
            }
          ],
          "value": "Upgrade to Kong Mesh 2.13.10 or 2.14.2, whichever matches your release line. In patched versions a dataplane whose identity derives from the kuma.io/workload label requires a workload-bound token; an unbound tags-only token is rejected at XDS authentication. Kubernetes mode and universal templates that do not reference the workload label keep working with unbound tokens."
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "timeline": [
        {
          "lang": "en",
          "time": "2026-08-01T16:58:00.000Z",
          "value": "Kong Mesh 2.13.10 and 2.14.2 published"
        }
      ],
      "title": "Kong Mesh: a dataplane token without a workload binding can claim any workload\u0027s SPIFFE identity",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIssue workload-bound dataplane tokens for every dataplane whose identity derives from the \u003ccode\u003ekuma.io/workload\u003c/code\u003e label. A workload-bound token constrains that label to the bound value, so a mismatched label is rejected at authentication.\u003c/p\u003e"
            }
          ],
          "value": "Issue workload-bound dataplane tokens for every dataplane whose identity derives from the kuma.io/workload label. A workload-bound token constrains that label to the bound value, so a mismatched label is rejected at authentication."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
    "assignerShortName": "Kong",
    "cveId": "CVE-2026-18677",
    "datePublished": "2026-08-12T18:47:06.710Z",
    "dateReserved": "2026-08-03T15:20:45.630Z",
    "dateUpdated": "2026-08-13T14:49:27.614Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-18677",
      "date": "2026-11-11",
      "epss": "0.00583",
      "percentile": "0.48334"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "modules": [
                  "kuma-cp"
                ],
                "platforms": [
                  "Linux"
                ],
                "product": "Kong Mesh",
                "vendor": "Kong Inc.",
                "versions": [
                  {
                    "lessThan": "2.13.10",
                    "status": "affected",
                    "version": "2.13.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "2.14.2",
                    "status": "affected",
                    "version": "2.14.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane\u0027s kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload\u0027s SPIFFE identity."
          },
          {
            "lang": "es",
            "value": "En Kong Mesh ejecut\u00e1ndose en modo universal con una MeshIdentity cuyo patr\u00f3n de ruta de ID SPIFFE deriva de la etiqueta kuma.io/workload del dataplane, el autenticador XDS en kuma-cp valida esa etiqueta solo cuyo el token del dataplane est\u00e1 vinculado a una carga de trabajo. La vinculaci\u00f3n de la carga de trabajo es opcional, por lo que un dataplane que presenta un token vinculado a etiquetas puede registrarse con kuma.io/workload establecido en cualquier valor y obtener la identidad SPIFFE de otra carga de trabajo."
          }
        ],
        "id": "CVE-2026-18677",
        "lastModified": "2026-10-23T19:10:00.167",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 6.0,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "HIGH",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-18677",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-13T14:49:14.103209Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-08-12T19:17:31.063",
        "references": [
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://developer.konghq.com/mesh/changelog/"
          },
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://github.com/kumahq/kuma/pull/17474"
          },
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://github.com/kumahq/kuma/pull/17502"
          },
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://github.com/kumahq/kuma/pull/17503"
          },
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://github.com/kumahq/kuma/security/advisories/GHSA-744g-c785-x65q"
          }
        ],
        "sourceIdentifier": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-290"
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-18677",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-13T14:49:14.103209Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-13T14:49:24.390Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "modules": [
                "kuma-cp"
              ],
              "platforms": [
                "Linux"
              ],
              "product": "Kong Mesh",
              "vendor": "Kong Inc.",
              "versions": [
                {
                  "lessThan": "2.13.10",
                  "status": "affected",
                  "version": "2.13.0",
                  "versionType": "semver"
                },
                {
                  "lessThan": "2.14.2",
                  "status": "affected",
                  "version": "2.14.0",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "configurations": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eYou are affected if all of the following hold:\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe control plane runs in universal mode.\u003c/li\u003e\u003cli\u003eA \u003ccode\u003eMeshIdentity\u003c/code\u003e is configured whose SPIFFE ID path template derives from the workload label, including the default universal template \u003ccode\u003e/workload/{{ .Workload }}\u003c/code\u003e.\u003c/li\u003e\u003cli\u003eDataplanes authenticate with tokens that are not bound to a workload (tags-bound tokens, the common case, since workload binding is newer and optional).\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eYou are not affected if:\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe control plane runs in Kubernetes mode. Its identity template is \u003ccode\u003e/ns/{{ .Namespace }}/sa/{{ .ServiceAccount }}\u003c/code\u003e, and the control plane derives those values from the pod\u0027s real identity rather than from a label the workload sets.\u003c/li\u003e\u003cli\u003eYour \u003ccode\u003eMeshIdentity\u003c/code\u003e uses a SPIFFE template that does not reference the workload label.\u003c/li\u003e\u003cli\u003eEvery dataplane whose identity derives from the workload label already uses a workload-bound token.\u003c/li\u003e\u003c/ul\u003e"
                }
              ],
              "value": "You are affected if all of the following hold:\n\n  *  The control plane runs in universal mode.\n  *  A MeshIdentity is configured whose SPIFFE ID path template derives from the workload label, including the default universal template /workload/{{ .Workload }}.\n  *  Dataplanes authenticate with tokens that are not bound to a workload (tags-bound tokens, the common case, since workload binding is newer and optional).\n\n\n\n\nYou are not affected if:\n\n  *  The control plane runs in Kubernetes mode. Its identity template is /ns/{{ .Namespace }}/sa/{{ .ServiceAccount }}, and the control plane derives those values from the pod\u0027s real identity rather than from a label the workload sets.\n  *  Your MeshIdentity uses a SPIFFE template that does not reference the workload label.\n  *  Every dataplane whose identity derives from the workload label already uses a workload-bound token."
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "finder",
              "value": "kanywst"
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eIn Kong Mesh running in universal mode with a \u003ccode\u003eMeshIdentity\u003c/code\u003e whose SPIFFE ID path template derives from the dataplane\u0027s \u003ccode\u003ekuma.io/workload\u003c/code\u003e label, the XDS authenticator in \u003ccode\u003ekuma-cp\u003c/code\u003e validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with \u003ccode\u003ekuma.io/workload\u003c/code\u003e set to any value and obtain another workload\u0027s SPIFFE identity.\u003c/p\u003e"
                }
              ],
              "value": "In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane\u0027s kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload\u0027s SPIFFE identity."
            }
          ],
          "impacts": [
            {
              "descriptions": [
                {
                  "lang": "en",
                  "value": "Workload identity spoofing"
                }
              ]
            }
          ],
          "metrics": [
            {
              "cvssV4_0": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "baseScore": 6,
                "baseSeverity": "MEDIUM",
                "exploitMaturity": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "HIGH",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-290",
                  "description": "CWE-290 Authentication Bypass by Spoofing",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-12T18:47:06.710Z",
            "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "shortName": "Kong"
          },
          "references": [
            {
              "name": "Upstream advisory GHSA-744g-c785-x65q",
              "tags": [
                "vendor-advisory"
              ],
              "url": "https://github.com/kumahq/kuma/security/advisories/GHSA-744g-c785-x65q"
            },
            {
              "name": "kumahq/kuma#17474 (master)",
              "tags": [
                "patch"
              ],
              "url": "https://github.com/kumahq/kuma/pull/17474"
            },
            {
              "name": "kumahq/kuma#17503 (release-2.13 backport)",
              "tags": [
                "patch"
              ],
              "url": "https://github.com/kumahq/kuma/pull/17503"
            },
            {
              "name": "kumahq/kuma#17502 (release-2.14 backport)",
              "tags": [
                "patch"
              ],
              "url": "https://github.com/kumahq/kuma/pull/17502"
            },
            {
              "name": "Kong MESH Changelog",
              "tags": [
                "release-notes"
              ],
              "url": "https://developer.konghq.com/mesh/changelog/"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eUpgrade to Kong Mesh 2.13.10 or 2.14.2, whichever matches your release line. In patched versions a dataplane whose identity derives from the \u003ccode\u003ekuma.io/workload\u003c/code\u003e label requires a workload-bound token; an unbound tags-only token is rejected at XDS authentication. Kubernetes mode and universal templates that do not reference the workload label keep working with unbound tokens.\u003c/p\u003e"
                }
              ],
              "value": "Upgrade to Kong Mesh 2.13.10 or 2.14.2, whichever matches your release line. In patched versions a dataplane whose identity derives from the kuma.io/workload label requires a workload-bound token; an unbound tags-only token is rejected at XDS authentication. Kubernetes mode and universal templates that do not reference the workload label keep working with unbound tokens."
            }
          ],
          "source": {
            "discovery": "EXTERNAL"
          },
          "timeline": [
            {
              "lang": "en",
              "time": "2026-08-01T16:58:00.000Z",
              "value": "Kong Mesh 2.13.10 and 2.14.2 published"
            }
          ],
          "title": "Kong Mesh: a dataplane token without a workload binding can claim any workload\u0027s SPIFFE identity",
          "workarounds": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eIssue workload-bound dataplane tokens for every dataplane whose identity derives from the \u003ccode\u003ekuma.io/workload\u003c/code\u003e label. A workload-bound token constrains that label to the bound value, so a mismatched label is rejected at authentication.\u003c/p\u003e"
                }
              ],
              "value": "Issue workload-bound dataplane tokens for every dataplane whose identity derives from the kuma.io/workload label. A workload-bound token constrains that label to the bound value, so a mismatched label is rejected at authentication."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "assignerShortName": "Kong",
        "cveId": "CVE-2026-18677",
        "datePublished": "2026-08-12T18:47:06.710Z",
        "dateReserved": "2026-08-03T15:20:45.630Z",
        "dateUpdated": "2026-08-13T14:49:27.614Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.