-Infinity
0

Vendor Risk Score

See how cncf compares to other vendors in security performance

View Risk Score →
EOL
Sep 30, 2026

End of life: 9/30/2026, Latest version: 3.14.0

First published (updated )
EOL
Jul 14, 2027

End of life: 7/14/2027, Latest version: 1.39.1

First published (updated )

Latest version: 3.7.1

First published (updated )
EOL
Jul 31, 2027

End of life: 7/31/2027, Latest version: 3.13.2

First published (updated )
Severity
5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

A vulnerability was found in Envoy, where using SDS with Combined Validation Context Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not applied, even though it was visible in the active config dump.

1 / 2
Source: Red Hat
First published (updated )
Severity
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

A vulnerability was found in Envoy version 1.13.0 or earlier may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks.

1 / 2
Source: Red Hat
First published (updated )
Severity
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

A vulnerability was found in Envoy version 1.13.0 or earlier may consume excessive amounts of memory when responding internally to pipelined requests.

1 / 2
Source: Red Hat
First published (updated )
EOL
Jul 9, 2026

End of life: 7/9/2026, Latest version: 3.12.0

First published (updated )
EOL
Apr 30, 2028
Support Ends
Apr 30, 2028

End of life: 4/30/2028, End of support: 4/30/2028, Latest version: 2.3.5

First published (updated )
EOL
Apr 23, 2027

End of life: 4/23/2027, Latest version: 1.38.4

First published (updated )
EOL
Jun 28, 2027
Support Ends
Apr 28, 2027

End of life: 6/28/2027, End of support: 4/28/2027, Latest version: 1.36.4

First published (updated )
EOL
May 14, 2026

End of life: 5/14/2026, Latest version: 3.11.3

First published (updated )
EOL
Apr 8, 2026

End of life: 4/8/2026, Latest version: 3.10.0

First published (updated )
EOL
Jan 13, 2027

End of life: 1/13/2027, Latest version: 1.37.6

First published (updated )
EOL
Feb 17, 2026

End of life: 2/17/2026, Latest version: 3.9.1

First published (updated )
EOL
Feb 28, 2027
Support Ends
Dec 28, 2026

End of life: 2/28/2027, End of support: 12/28/2026, Latest version: 1.35.8

First published (updated )
EOL
Jan 9, 2026

End of life: 1/9/2026, Latest version: 3.8.1

First published (updated )
EOL
Nov 6, 2026
Support Ends
Nov 6, 2026

End of life: 11/6/2026, End of support: 11/6/2026, Latest version: 2.2.8

First published (updated )
EOL
Nov 26, 2025

End of life: 11/26/2025, Latest version: 3.7.3

First published (updated )
EOL
Oct 14, 2026

End of life: 10/14/2026, Latest version: 1.36.10

First published (updated )
EOL
Nov 2, 2025

End of life: 11/2/2025, Latest version: 3.6.0

First published (updated )
EOL
Oct 27, 2026
Support Ends
Aug 27, 2026

End of life: 10/27/2026, End of support: 8/27/2026, Latest version: 1.34.11

First published (updated )
EOL
Jul 23, 2026

End of life: 7/23/2026, Latest version: 1.35.13

First published (updated )
EOL
Jul 31, 2026

End of life: 7/31/2026, Latest version: 3.5.5

First published (updated )
EOL
Jun 28, 2025

End of life: 6/28/2025, Latest version: 3.4.2

First published (updated )

Latest version: 3.6.14

First published (updated )
EOL
Jul 3, 2026
Support Ends
May 5, 2026

End of life: 7/3/2026, End of support: 5/5/2026, Latest version: 2.1.9

First published (updated )
Severity
6.8
EPSS
0.05%
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

CNCF K3s 1.32 before 1.32.4-rc1+k3s1 has a Kubernetes kubelet configuration change with the unintended consequence that, in some situations, ReadOnlyPort is set to 10255. For example, the default behavior of a K3s online installation might allow unauthenticated access to this port, exposing credentials.

First published (updated )
EOL
Jun 28, 2026
Support Ends
Apr 28, 2026

End of life: 6/28/2026, End of support: 4/28/2026, Latest version: 1.33.13

First published (updated )
Severity
4

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values).

https://github.com/helm/helm/issues/7275 https://www.cncf.io/projects/helm/

First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203