CVE-2026-71566 json
KubeVirt backend is not authenticated
published 2mo ago modified 2mo ago also EUVD-2026-60205 , GHSA-qpfr-jqjq-v83w
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository openshift-metal3/fakefish. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 9.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
FakeFish handles incoming credentials by passing them down to scripts. This works for real hardware because in the end it's up to the BMC to validate them. However, KubeVirt relies on a KUBECONFIG file mounted to the container and completely ignores the credentials. This allows any user of the cluster to control VMs of the user that created fakefish, power them on and off, and mount arbitrary CD images to them.
Is CVE-2026-71566 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H |
Affected products
- openshift-metal3 fakefish
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/openshift-metal3/fakefish/security/advisories/GHSA-qpfr-jqjq-v83w
vendor-advisory, advisory
Sources
- CVE List CVE-2026-71566
- NVD CVE-2026-71566
- Maintainer advisory GHSA-qpfr-jqjq-v83w
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of openshift-metal3/fakefish published their own advisory on GitHub. Reviewed sources take precedence over it.