{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-88979","id":"CVE-2026-88979","title":"Kubeflow Pipelines token forgery in TensorBoard proxy","description":"Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. From 2.17.0 until 2.18.0, the TensorBoard proxy token introduced by the incomplete remediation for CVE-2026-54745 uses MINIO_SECRET_KEY as its HMAC secret, whose bundled default is publicly known. In an authorization-disabled deployment using that default, an unauthenticated attacker can forge a tok","descriptionLong":"Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. From 2.17.0 until 2.18.0, the TensorBoard proxy token introduced by the incomplete remediation for CVE-2026-54745 uses MINIO_SECRET_KEY as its HMAC secret, whose bundled default is publicly known. In an authorization-disabled deployment using that default, an unauthenticated attacker can forge a token containing a chosen viewerName and namespace; the proxy constructs the destination from the viewerName plus the -service suffix, the namespace, and the configured cluster domain, then reads responses on port 80 under the /tensorboard/<viewer>/ path. Resource-name validation and path-traversal rejection remain enforced, authorization-enabled deployments still check access to the selected namespace, and unrestricted metadata access, writes, or service disruption are not established. This issue is fixed in version 2.18.0.","published":"2026-11-05T22:14:38.071Z","updated":"2026-11-08T02:30:32.972588505Z","reserved":"2026-09-10T16:02:31.342Z","status":"Awaiting Analysis","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","rating":"medium","source":"GitHub_M"},"metrics":[{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","rating":"medium","source":"GitHub_M"},{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","rating":"medium","source":"github.com"},{"version":"3.1","score":5.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","rating":"medium","source":"OSV"}],"rating":"medium","products":["kubeflow pipelines"],"affectedProducts":[{"vendor":"kubeflow","product":"pipelines","defaultStatus":null,"versions":[{"version":">= 2.17.0, < 2.18.0","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-798","CWE-918"],"aliases":["GHSA-j429-j7xw-8j9h"],"references":[{"url":"https://github.com/kubeflow/pipelines/security/advisories/GHSA-j429-j7xw-8j9h","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/kubeflow/pipelines/pull/14346","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/kubeflow/pipelines/commit/c8effaed62476a8d8c99d3a6cfdd404a04ef99d8","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/kubeflow/pipelines/releases/tag/2.18.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88979.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-88979","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"partial"},"epss":0.00232,"epssPercentile":0.14245,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-88979","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-88979","ok":true,"note":"Awaiting Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-88979","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-88979","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}