CVE-2026-40868: kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token

kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token

F-KYVERNO-APICALL-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

8.1high

CVE-2026-40868CVEkyverno/kyverno

kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token

Fixed in: 1.16.4

patched

details

Finding IDs: F-KYVERNO-APICALL-001
CVE: CVE-2026-40868
GHSA: GHSA-q93q-v844-jrqp
Status: patched
Fixed in: 1.16.4
Recorded credit: reporter: @1seal
Note: GHSA-q93q-v844-jrqp
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVE registry state: PUBLISHED
CVE state checked: 23 Sep 2026
Upstream title: kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token
Upstream publication: 13 Apr 2026
Upstream updated: 30 Jun 2026
Metadata fetched: 23 Sep 2026
Upstream @1seal credit: @1seal: reporter (accepted)

F-KYVERNO-APICALL-001: Outbound request trust. A policy-controlled API destination receives ambient credentials. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-KYVERNO-APICALL-001

Security area (1seal assessment): Authorization. A policy-controlled API destination receives ambient credentials. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.