CVE-2026-33413
etcd: Authorization bypasses in multiple APIs
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
8.8
etcd: Authorization bypasses in multiple APIs
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
CVE-2026-33413- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-862
- Updated
- 2026-11-02
EUVDEUVD-2026-16191
8.8
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
EUVD-2026-16191- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-q8m4-xhhv-38mg
8.8
etcd: Authorization bypasses in multiple APIs
Impact
What kind of vulnerability is it? Who is impacted?
Multiple vulnerabilities allow unauthorized users to bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients.
In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to:
- call MemberList and learn cluster topology, including member IDs and advertised endpoints
- call Alarm, which can be abused for operational disruption or denial of service
- use Lease APIs, interfering with TTL-based keys and lease ownership
- trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows
Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected.
Patches
Has the problem been patched? What versions should users upgrade to?
These vulnerabilities are patched in the following versions:
- etcd 3.6.9
- etcd 3.5.28
- etcd 3.4.42
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
- restrict network access to etcd server ports so only trusted components can connect
- require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution
Reporters
Community efforts help keep etcd secure
The etcd community thanks Isaac David, bugbunny.ai, Asim Viladi Oglu Manizada, Alex Schapiro & Ahmed Allam from Strix security, Luke Francis, and @OLU-DEVX for reporting these vulnerabilities.
Dependency Between Reported Issues
These issues all originate from the same underlying flaw in the gRPC API layer.
They affect the same API surface and share a common root cause. In practice, the fix is implemented as a single, unified change at the API layer, which resolves all issues together.
Given this, we believe these issues are best treated as a single vulnerability and should be assigned a single CVE.
- Record
GHSA-q8m4-xhhv-38mg- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-862
- Updated
- 2026-11-02
NVD
8.8
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
CVE-2026-33413- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/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 - CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-862
- Updated
- 2026-11-02
OSVALPINE-CVE-2026-33413
8.8
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
ALPINE-CVE-2026-33413- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-03
OSV
8.8
etcd: Authorization bypasses in multiple APIs
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
CVE-2026-33413- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-862
- Updated
- 2026-11-02
Show 10 moreShow less
OSVDEBIAN-CVE-2026-33413
8.8
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
DEBIAN-CVE-2026-33413- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-q8m4-xhhv-38mg
8.8
etcd: Authorization bypasses in multiple APIs
Impact
What kind of vulnerability is it? Who is impacted?
Multiple vulnerabilities allow unauthorized users to bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients.
In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to:
- call MemberList and learn cluster topology, including member IDs and advertised endpoints
- call Alarm, which can be abused for operational disruption or denial of service
- use Lease APIs, interfering with TTL-based keys and lease ownership
- trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows
Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected.
Patches
Has the problem been patched? What versions should users upgrade to?
These vulnerabilities are patched in the following versions:
- etcd 3.6.9
- etcd 3.5.28
- etcd 3.4.42
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
- restrict network access to etcd server ports so only trusted components can connect
- require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution
Reporters
Community efforts help keep etcd secure
The etcd community thanks Isaac David, bugbunny.ai, Asim Viladi Oglu Manizada, Alex Schapiro & Ahmed Allam from Strix security, Luke Francis, and @OLU-DEVX for reporting these vulnerabilities.
Dependency Between Reported Issues
These issues all originate from the same underlying flaw in the gRPC API layer.
They affect the same API surface and share a common root cause. In practice, the fix is implemented as a single, unified change at the API layer, which resolves all issues together.
Given this, we believe these issues are best treated as a single vulnerability and should be assigned a single CVE.
- Record
GHSA-q8m4-xhhv-38mg- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - Weakness
- CWE-862
- Updated
- 2026-11-02
OSVRHSA-2026:28047
9.1
Red Hat Security Advisory: Red Hat OpenStack Platform 17.1 (etcd) security update
- Record
RHSA-2026:28047- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:54757
9.1
Red Hat Security Advisory: Red Hat OpenStack Platform 16.2 security advisory
- Record
RHSA-2026:54757- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-33413
8.8
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
UBUNTU-CVE-2026-33413- CVSS 4.0
- 8.8 High
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N - CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVAZL-80957 No score
CVE-2026-33413 affecting package etcd for versions less than 3.5.28-1
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
AZL-80957- Updated
- 2026-11-02
OSVBIT-etcd-2026-33413 No score
etcd: Authorization bypasses in multiple APIs
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
- Record
BIT-etcd-2026-33413- Updated
- 2026-11-02
OSVGO-2026-4806 No score
Authorization bypasses in multiple APIs in go.etcd.io/etcd
Authorization bypasses in multiple APIs in go.etcd.io/etcd
- Record
GO-2026-4806- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10562-1 No score
flannel-0.28.4-1.1 on GA media
These are all security issues fixed in the flannel-0.28.4-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10562-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
go.etcd.io/etcd/v3Go |
3.6.0-alpha.0 to 3.6.8 | 3.6.9 |
go.etcd.io/etcd/v3Go |
3.5.0-alpha.0 to 3.5.27 | 3.5.28 |
go.etcd.io/etcd/v3Go |
through 3.4.41 | 3.4.42 |
go.etcd.io/etcdGo |
through 3.3.27 | None known |
etcdAlpine:v3.23 |
3.5.0 up to 3.6.10-r0 | 3.6.10-r0 |
etcdAlpine:v3.24 |
3.5.0 up to 3.6.10-r0 | 3.6.10-r0 |
etcdAzure Linux:3 |
before 3.5.28-1 | 3.5.28-1 |
etcdBitnami |
before 3.4.42, 3.5.0 up to 3.5.28, 3.6.0 up to 3.6.9 | 3.4.423.5.283.6.9 |
etcdDebian:12 |
All versions, plus listed versions 3.4.23-43.4.23-53.4.23-63.4.30-13.4.30-2 Show 25 moreShow less3.4.30-33.5.15-13.5.15-23.5.15-33.5.15-43.5.15-53.5.15-63.5.15-73.5.16-13.5.16-103.5.16-113.5.16-23.5.16-33.5.16-43.5.16-53.5.16-63.5.16-73.5.16-83.5.16-93.5.22-13.5.22-23.5.30-1~exp13.5.30-1~exp23.5.30-23.5.5-1 |
None known |
etcdDebian:13 |
All versions, plus listed versions 3.5.16-103.5.16-113.5.16-43.5.16-53.5.16-6 Show 8 moreShow less3.5.16-73.5.16-83.5.16-93.5.22-13.5.22-23.5.30-1~exp13.5.30-1~exp23.5.30-2 |
None known |
Show 76 moreShow less
| Package | Affected | Fixed |
|---|---|---|
etcdDebian:14 |
before 3.5.16-11, plus listed versions 3.5.16-103.5.16-43.5.16-53.5.16-63.5.16-73.5.16-83.5.16-9 |
3.5.16-11 |
go.etcd.io/etcd/v3Go |
3.6.0-alpha.0 up to 3.6.9 | 3.6.9 |
go.etcd.io/etcd/v3Go |
3.5.0-alpha.0 up to 3.5.28 | 3.5.28 |
go.etcd.io/etcd/v3Go |
before 3.4.42 | 3.4.42 |
go.etcd.io/etcdGo |
All versions | None known |
go.etcd.io/etcd/v3Go |
before 3.4.42, 3.5.0-alpha.0 up to 3.5.28, 3.6.0-alpha.0 up to 3.6.9 | 3.4.423.5.283.6.9 |
etcdRed Hat:openstack:17.1::el9 From an advisory covering 11 CVEs |
before 0:3.4.26-9.5.el9ost | 0:3.4.26-9.5.el9ost |
etcd-debuginfoRed Hat:openstack:17.1::el9 From an advisory covering 11 CVEs |
before 0:3.4.26-9.5.el9ost | 0:3.4.26-9.5.el9ost |
etcd-debugsourceRed Hat:openstack:17.1::el9 From an advisory covering 11 CVEs |
before 0:3.4.26-9.5.el9ost | 0:3.4.26-9.5.el9ost |
collectd-sensubilityRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:0.2.1-1.1.el8ost | 0:0.2.1-1.1.el8ost |
collectd-sensubility-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:0.2.1-1.1.el8ost | 0:0.2.1-1.1.el8ost |
etcdRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:3.3.23-22.el8ost | 0:3.3.23-22.el8ost |
etcd-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:3.3.23-22.el8ost | 0:3.3.23-22.el8ost |
etcd-debugsourceRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:3.3.23-22.el8ost | 0:3.3.23-22.el8ost |
openstack-keystoneRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:16.0.3-2.20260616134936.9d699a7.el8ost | 1:16.0.3-2.20260616134936.9d699a7.el8ost |
python3-keystoneRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:16.0.3-2.20260616134936.9d699a7.el8ost | 1:16.0.3-2.20260616134936.9d699a7.el8ost |
python-pyasn1Red Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:0.4.6-4.el8ost | 0:0.4.6-4.el8ost |
python3-pyasn1Red Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:0.4.6-4.el8ost | 0:0.4.6-4.el8ost |
python3-pyasn1-modulesRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:0.4.6-4.el8ost | 0:0.4.6-4.el8ost |
openstack-novaRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-apiRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-commonRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-computeRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-conductorRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-consoleRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-migrationRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-novncproxyRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-schedulerRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-serialproxyRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-nova-spicehtml5proxyRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
python3-novaRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:20.6.2-2.20260317135026.8a24acd.el8ost | 1:20.6.2-2.20260317135026.8a24acd.el8ost |
openstack-glanceRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:19.0.5-2.20260512165254.eb6ad61.el8ost | 1:19.0.5-2.20260512165254.eb6ad61.el8ost |
python3-glanceRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 1:19.0.5-2.20260512165254.eb6ad61.el8ost | 1:19.0.5-2.20260512165254.eb6ad61.el8ost |
erlangRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-asn1Red Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-asn1-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-compilerRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-cryptoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-crypto-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-debugsourceRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-eldapRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-erl_interface-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-ertsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-erts-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-hipeRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-inetsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-kernelRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-mnesiaRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-odbc-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-os_monRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-os_mon-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-parsetoolsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-public_keyRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-runtime_toolsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-runtime_tools-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-saslRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-snmpRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-sslRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-stdlibRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-syntax_toolsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-toolsRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-tools-debuginfoRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
erlang-xmerlRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:23.3.4.18-2.el8ost | 0:23.3.4.18-2.el8ost |
python-oslo-messagingRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:10.2.4-2.20260710155333.82281a0.el8ost | 0:10.2.4-2.20260710155333.82281a0.el8ost |
python3-oslo-messagingRed Hat:openstack:16.2::el8 From an advisory covering 24 CVEs |
before 0:10.2.4-2.20260710155333.82281a0.el8ost | 0:10.2.4-2.20260710155333.82281a0.el8ost |
etcdUbuntu:16.04:LTS |
All versions, plus listed versions 2.2.0+dfsg-22.2.1+dfsg-12.2.2+dfsg-12.2.2+dfsg-22.2.3+dfsg-12.2.5+dfsg-12.2.5+dfsg-1ubuntu1 |
None known |
etcdUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 3.1.0-13.2.9+dfsg-23.2.9+dfsg-33.2.17+dfsg-13.2.17+dfsg-1ubuntu0.1~esm13.2.17+dfsg-1ubuntu0.13.2.17+dfsg-1ubuntu0.1+esm13.2.17+dfsg-1ubuntu0.1+esm2 |
None known |
etcdUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 3.2.26+dfsg-33.2.26+dfsg-43.2.26+dfsg-63.2.26+dfsg-6ubuntu0.13.2.26+dfsg-6ubuntu0.23.2.26+dfsg-6ubuntu0.2+esm1 |
None known |
etcdUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 3.3.25+dfsg-63.3.25+dfsg-73.3.25+dfsg-7ubuntu0.22.04.13.3.25+dfsg-7ubuntu0.22.04.1+esm13.3.25+dfsg-7ubuntu0.22.04.23.3.25+dfsg-7ubuntu0.22.04.2+esm13.3.25+dfsg-7ubuntu0.22.04.2+esm23.3.25+dfsg-7ubuntu0.22.04.2+esm3 |
None known |
etcdUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 3.4.23-4ubuntu23.4.30-13.4.30-1build13.4.30-1ubuntu0.24.04.13.4.30-1ubuntu0.24.04.2 Show 4 moreShow less3.4.30-1ubuntu0.24.04.2+esm13.4.30-1ubuntu0.24.04.33.4.30-1ubuntu0.24.04.3+esm13.4.30-1ubuntu0.24.04.3+esm2 |
None known |
etcdUbuntu:25.10 |
All versions, plus listed versions 3.5.16-4 |
None known |
etcdUbuntu:26.10 |
All versions, plus listed versions 3.5.16-103.5.30-2 |
None known |
etcdUbuntu:Pro:26.04:LTS |
All versions, plus listed versions 3.5.16-43.5.16-103.5.16-10ubuntu0.26.04.1~esm1 |
None known |
flannelopenSUSE:Tumbleweed |
before 0.28.4-1.1 | 0.28.4-1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-33413 is a high vulnerability (CVSS 8.8) in Etcd, published March 20, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 17th percentile. Fixed in go.etcd.io/etcd/v3 3.6.9.
References
github.com/etcd-io/etcd/security/advisories/GHSA-q8m4-xhhv-38mg
nvd.nist.gov/vuln/detail/CVE-2026-33413
github.com/advisories/GHSA-q8m4-xhhv-38mg
security.alpinelinux.org/vuln/CVE-2026-33413
github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33413.json
security-tracker.debian.org/tracker/CVE-2026-33413
Show 194 moreShow less
github.com/etcd-io/etcd
access.redhat.com/errata/RHSA-2026:28047
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=2418462
bugzilla.redhat.com/show_bug.cgi?id=2434432
bugzilla.redhat.com/show_bug.cgi?id=2437111
bugzilla.redhat.com/show_bug.cgi?id=2445356
bugzilla.redhat.com/show_bug.cgi?id=2449833
bugzilla.redhat.com/show_bug.cgi?id=2451728
bugzilla.redhat.com/show_bug.cgi?id=2456336
bugzilla.redhat.com/show_bug.cgi?id=2456338
bugzilla.redhat.com/show_bug.cgi?id=2456339
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_28047.json
access.redhat.com/security/cve/CVE-2025-61726
cve.org/CVERecord?id=CVE-2025-61726
nvd.nist.gov/vuln/detail/CVE-2025-61726
go.dev/cl/736712
go.dev/issue/77101
groups.google.com/g/golang-announce/c/Vd2tYVM8eUc
pkg.go.dev/vuln/GO-2026-4341
access.redhat.com/security/cve/CVE-2025-61729
cve.org/CVERecord?id=CVE-2025-61729
nvd.nist.gov/vuln/detail/CVE-2025-61729
go.dev/cl/725920
go.dev/issue/76445
groups.google.com/g/golang-announce/c/8FJoBkPddm4
pkg.go.dev/vuln/GO-2025-4155
access.redhat.com/security/cve/CVE-2025-68121
cve.org/CVERecord?id=CVE-2025-68121
nvd.nist.gov/vuln/detail/CVE-2025-68121
go.dev/cl/737700
go.dev/issue/77217
groups.google.com/g/golang-announce/c/K09ubi9FQFk
pkg.go.dev/vuln/GO-2026-4337
access.redhat.com/security/cve/CVE-2026-25679
cve.org/CVERecord?id=CVE-2026-25679
nvd.nist.gov/vuln/detail/CVE-2026-25679
go.dev/cl/752180
go.dev/issue/77578
groups.google.com/g/golang-announce/c/EdhZqrQ98hk
pkg.go.dev/vuln/GO-2026-4601
access.redhat.com/security/cve/CVE-2026-27137
bugzilla.redhat.com/show_bug.cgi?id=2445345
cve.org/CVERecord?id=CVE-2026-27137
nvd.nist.gov/vuln/detail/CVE-2026-27137
go.dev/cl/752182
go.dev/issue/77952
pkg.go.dev/vuln/GO-2026-4599
access.redhat.com/security/cve/CVE-2026-32280
cve.org/CVERecord?id=CVE-2026-32280
nvd.nist.gov/vuln/detail/CVE-2026-32280
go.dev/cl/758320
go.dev/issue/78282
groups.google.com/g/golang-announce/c/0uYbvbPZRWU
pkg.go.dev/vuln/GO-2026-4947
access.redhat.com/security/cve/CVE-2026-32282
cve.org/CVERecord?id=CVE-2026-32282
nvd.nist.gov/vuln/detail/CVE-2026-32282
go.dev/cl/763761
go.dev/issue/78293
pkg.go.dev/vuln/GO-2026-4864
access.redhat.com/security/cve/CVE-2026-32283
cve.org/CVERecord?id=CVE-2026-32283
nvd.nist.gov/vuln/detail/CVE-2026-32283
go.dev/cl/763767
go.dev/issue/78334
pkg.go.dev/vuln/GO-2026-4870
access.redhat.com/security/cve/CVE-2026-33186
cve.org/CVERecord?id=CVE-2026-33186
nvd.nist.gov/vuln/detail/CVE-2026-33186
github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3
access.redhat.com/security/cve/CVE-2026-33413
cve.org/CVERecord?id=CVE-2026-33413
access.redhat.com/security/cve/CVE-2026-33810
bugzilla.redhat.com/show_bug.cgi?id=2456335
cve.org/CVERecord?id=CVE-2026-33810
nvd.nist.gov/vuln/detail/CVE-2026-33810
go.dev/cl/763763
go.dev/issue/78332
pkg.go.dev/vuln/GO-2026-4866
access.redhat.com/errata/RHSA-2026:54757
bugzilla.redhat.com/show_bug.cgi?id=2415344
bugzilla.redhat.com/show_bug.cgi?id=2430312
bugzilla.redhat.com/show_bug.cgi?id=2430472
bugzilla.redhat.com/show_bug.cgi?id=2440368
bugzilla.redhat.com/show_bug.cgi?id=2451037
bugzilla.redhat.com/show_bug.cgi?id=2456333
bugzilla.redhat.com/show_bug.cgi?id=2464305
bugzilla.redhat.com/show_bug.cgi?id=2467822
bugzilla.redhat.com/show_bug.cgi?id=2480756
bugzilla.redhat.com/show_bug.cgi?id=2482093
bugzilla.redhat.com/show_bug.cgi?id=2482286
bugzilla.redhat.com/show_bug.cgi?id=2484207
bugzilla.redhat.com/show_bug.cgi?id=2484835
issues.redhat.com/browse/OSPRH-20808
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54757.json
access.redhat.com/security/cve/CVE-2025-65073
cve.org/CVERecord?id=CVE-2025-65073
nvd.nist.gov/vuln/detail/CVE-2025-65073
security.openstack.org/ossa/OSSA-2025-002.html
openwall.com/lists/oss-security/2025/11/04/2
access.redhat.com/security/cve/CVE-2026-23490
cve.org/CVERecord?id=CVE-2026-23490
nvd.nist.gov/vuln/detail/CVE-2026-23490
github.com/pyasn1/pyasn1/commit/3908f144229eed4df24bd569d16e5991ace44970
github.com/pyasn1/pyasn1/releases/tag/v0.6.2
github.com/pyasn1/pyasn1/security/advisories/GHSA-63vm-454h-vhhq
access.redhat.com/security/cve/CVE-2026-24708
cve.org/CVERecord?id=CVE-2026-24708
nvd.nist.gov/vuln/detail/CVE-2026-24708
bugs.launchpad.net/nova/+bug/2137507
access.redhat.com/security/cve/CVE-2026-27145
cve.org/CVERecord?id=CVE-2026-27145
nvd.nist.gov/vuln/detail/CVE-2026-27145
go.dev/cl/783621
go.dev/issue/79694
groups.google.com/g/golang-announce/c/tKs3rmcBcKw
pkg.go.dev/vuln/GO-2026-5037
access.redhat.com/security/cve/CVE-2026-32281
cve.org/CVERecord?id=CVE-2026-32281
nvd.nist.gov/vuln/detail/CVE-2026-32281
go.dev/cl/758061
go.dev/issue/78281
pkg.go.dev/vuln/GO-2026-4946
access.redhat.com/security/cve/CVE-2026-33551
cve.org/CVERecord?id=CVE-2026-33551
nvd.nist.gov/vuln/detail/CVE-2026-33551
openwall.com/lists/oss-security/2026/04/07/12
security.openstack.org/ossa/OSSA-2026-005.html
access.redhat.com/security/cve/CVE-2026-33811
cve.org/CVERecord?id=CVE-2026-33811
nvd.nist.gov/vuln/detail/CVE-2026-33811
go.dev/cl/767860
go.dev/issue/78803
groups.google.com/g/golang-announce/c/qcCIEXso47M
pkg.go.dev/vuln/GO-2026-4981
access.redhat.com/security/cve/CVE-2026-34881
cve.org/CVERecord?id=CVE-2026-34881
nvd.nist.gov/vuln/detail/CVE-2026-34881
bugs.launchpad.net/glance/+bug/2138602
access.redhat.com/security/cve/CVE-2026-39821
cve.org/CVERecord?id=CVE-2026-39821
nvd.nist.gov/vuln/detail/CVE-2026-39821
groups.google.com/g/golang-announce/c/iI-mYSI0lu8
pkg.go.dev/vuln/GO-2026-5026
access.redhat.com/security/cve/CVE-2026-42789
cve.org/CVERecord?id=CVE-2026-42789
nvd.nist.gov/vuln/detail/CVE-2026-42789
cna.erlef.org/cves/CVE-2026-42789.html
github.com/erlang/otp/commit/471cd2f664300a95353c467873800bbe706005db
github.com/erlang/otp/commit/59c8d824386b2eb1614ff9340624843ef6aca0fd
github.com/erlang/otp/security/advisories/GHSA-c99q-jmpx-v8qq
osv.dev/vulnerability/EEF-CVE-2026-42789
erlang.org/doc/system/versions.html
cve.org/CVERecord?id=CVE-2026-42790
nvd.nist.gov/vuln/detail/CVE-2026-42790
cna.erlef.org/cves/CVE-2026-42790.html
github.com/erlang/otp/commit/0769050c69d73762672b0db1347b6993a5b31759
github.com/erlang/otp/commit/21abed64eb2026b5f82f432709e4e932f9be389a
github.com/erlang/otp/commit/fb67c6d1836f51105a96d8b769e71e4215a79457
github.com/erlang/otp/security/advisories/GHSA-22cw-4ph4-6447
osv.dev/vulnerability/EEF-CVE-2026-42790
cve.org/CVERecord?id=CVE-2026-43001
nvd.nist.gov/vuln/detail/CVE-2026-43001
bugs.launchpad.net/keystone/+bug/2149775
review.opendev.org/c/openstack/keystone/+/985804
cve.org/CVERecord?id=CVE-2026-44393
nvd.nist.gov/vuln/detail/CVE-2026-44393
bugs.launchpad.net/oslo.messaging/+bug/2150316
wiki.openstack.org/wiki/OSSN/OSSN-0096
ubuntu.com/security/CVE-2026-33413
suse.com/security/cve/CVE-2026-33413
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
suse.com/security/cve/CVE-2016-11068
suse.com/security/cve/CVE-2016-11069
suse.com/security/cve/CVE-2016-11070
suse.com/security/cve/CVE-2016-11071
suse.com/security/cve/CVE-2016-11072
suse.com/security/cve/CVE-2016-11073
suse.com/security/cve/CVE-2016-11074
suse.com/security/cve/CVE-2016-11075
suse.com/security/cve/CVE-2016-11076
suse.com/security/cve/CVE-2016-11077
suse.com/security/cve/CVE-2016-11078
suse.com/security/cve/CVE-2016-11079
suse.com/security/cve/CVE-2016-11080
suse.com/security/cve/CVE-2016-11081
suse.com/security/cve/CVE-2016-11082
suse.com/security/cve/CVE-2016-11083
suse.com/security/cve/CVE-2016-11084
suse.com/security/cve/CVE-2017-18870
suse.com/security/cve/CVE-2017-18871
Left out here: 1,716 references and the rest of 1 source description. The JSON record has them.