Change:
The section of the Changelog for 1.23.14 (and sibling bugfix releases) says that 1.23.13 both has the vuln and also has the fix. The Fix version should be 1.23.14 in the above and sibling changelogs. Load the link above. No response N/A N/A N/A N/A N/A N/A
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig docs
cc
For v1.23.14, the title is . This seems to be valid. means
You're looking at the wrong text. Follow the link and see .13 in both lists: kube-apiserver v1.25.0 - v1.25.3 kube-apiserver v1.24.0 - v1.24.7 kube-apiserver v1.23.0 - v1.23.13 kube-apiserver v1.22.0 - v1.22.15 kube-apiserver <= v1.21.? kube-apiserver v1.25.4 kube-apiserver v1.24.8 kube-apiserver v1.23.13 kube-apiserver v1.22.16
Got it. Thanks for pointing out the location.
I opened to fix it.
/reopen Can you please cherry-pick to the release branches (1.25-1.22)?
Reopened this issue. <detailsIn response to : /reopen Can you please cherry-pick to the release branches (1.25-1.22)? Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Of course. Done
Cherry-picks are done, thanks a lot /close
Closing this issue. <detailsIn response to : Cherry-picks are done, thanks a lot /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
- [CPU and Memory manager are not working correctly for Guaranteed Pods with multiple containers](#cpu-and-memory-manager-are-not-working-correctly-for-guaranteed-pods-with-multiple-containers) - [`CSIMigrationvSphere` feature gate has not migrated to new CRD APIs](#csimigrationvsphere-feature-gate-has-not-migrated-to-new-crd-apis) - [Workloads that saturate nodes with pods may see pods that fail due to node admission](#workloads-that-saturate-nodes-with-pods-may-see-pods-that-fail-due-to-node-admission) <del> - [Etcd v3.5.[0-2] data corruption](#etcd-v350-2-data-corruption) </del> <ins> - [Etcd v3.5.[0-2] data corruption](#etcd-v350-2-data-corruption) </ins> - [Urgent Upgrade Notes](#urgent-upgrade-notes) - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade) - [Changes by Kind](#changes-by-kind-15)

- [Urgent Upgrade Notes](#urgent-upgrade-notes) - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade) - [Known Issues](#known-issues) <del> - [Etcd v3.5.[0-2] data corruption](#etcd-v350-2-data-corruption) </del> <ins> - [Etcd v3.5.[0-2] data corruption](#etcd-v350-2-data-corruption) </ins> - [Changes by Kind](#changes-by-kind-14) - [Deprecation](#deprecation) - [API Change](#api-change-5)

**Fixed Versions**: - kube-apiserver v1.25.4 - kube-apiserver v1.24.8 <del> - kube-apiserver v1.23.13 </del> <ins> - kube-apiserver v1.23.14 </ins> - kube-apiserver v1.22.16 This vulnerability was reported by Richard Turnbull of NCC Group as part of the Kubernetes Audit

**Fixed Versions**: - kube-apiserver v1.25.4 - kube-apiserver v1.24.8 <del> - kube-apiserver v1.23.13 </del> <ins> - kube-apiserver v1.23.14 </ins> - kube-apiserver v1.22.16 This vulnerability was reported by Yuval Avrahami of Palo Alto Networks