Cncf

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any Cncf product.

RSS Feeds for Cncf security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in Cncf products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by Cncf Sorted by Most Security Vulnerabilities since 2018

Cncf Envoy3 vulnerabilities

Cncf Crossplane2 vulnerabilities

Cncf Harbor2 vulnerabilities

Cncf Spire2 vulnerabilities

Cncf Argo Continuous Delivery1 vulnerability

Cncf Cni Network Plugins1 vulnerability

Cncf Container Network Interface1 vulnerability

Cncf Knative Func1 vulnerability

Cncf Opentelemetry Go Contrib1 vulnerability

Cncf Portmap1 vulnerability

By the Year

In 2026 there have been 0 vulnerabilities in Cncf. Cncf did not have any published security vulnerabilities last year.

Year	Vulnerabilities	Average Score
2026	0	0.00
2025	0	0.00
2024	0	0.00
2023	3	6.67
2022	1	7.40
2021	3	7.45
2020	7	6.00
2019	1	7.50

It may take a day or so for new Cncf vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Cncf Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2023-38495	Jul 27, 2023	CVE-2023-38495 Crossplane image backend fails validation v<1.11.5/1.12.3/1.13.0 Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, Crossplane's image backend does not validate the byte contents of Crossplane packages. As such, Crossplane does not detect if an attacker has tampered with a Package. The problem has been fixed in 1.11.5, 1.12.3 and 1.13.0. As a workaround, only use images from trusted sources and keep Package editing/creating privileges to administrators only.	Crossplane
CVE-2023-37900	Jul 27, 2023	Crossplane pre-1.13.0 DoS via large image causing OOM Crossplane is a framework for building cloud native control planes without needing to write code. In versions prior to 1.11.5, 1.12.3, and 1.13.0, a high-privileged user could create a Package referencing an arbitrarily large image containing that Crossplane would then parse, possibly resulting in exhausting all the available memory and therefore in the container being OOMKilled. The impact is limited due to the high privileges required to be able to create the Package and the eventually consistency nature of controller. This issue is fixed in versions 1.11.5, 1.12.3, and 1.13.0.	Crossplane
CVE-2023-25151	Feb 08, 2023	opentelemetry-go-contrib otelhttp cardinality issue CVE-2023-25151 (pre-0.39) opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not "forget" previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.	Opentelemetry Go Contrib
CVE-2022-41939	Nov 19, 2022	Knative Func 1.8.x: Credential Leak via Malicious Buildpack (CVE-2022-41939) knative.dev/func is is a client library and CLI enabling the development and deployment of Kubernetes functions. Developers using a malicious or compromised third-party buildpack could expose their registry credentials or local docker socket to a malicious `lifecycle` container. This issues has been patched in PR #1442, and is part of release 1.8.1. This issue only affects users who are using function buildpacks from third-parties; pinning the builder image to a specific content-hash with a valid `lifecycle` image will also mitigate the attack.	Knative Func
CVE-2021-20206	Mar 26, 2021	An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1 An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1. When specifying the plugin to load in the 'type' field in the network configuration, it is possible to use special elements such as "../" separators to reference binaries elsewhere on the system. This flaw allows an attacker to execute other existing binaries other than the cni plugins/types, such as 'reboot'. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.	Container Network Interface
CVE-2021-27099	Mar 05, 2021	In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws_iid" Node Attestor improperly normalizes the path provided through the agent ID templating feature, which may In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws_iid" Node Attestor improperly normalizes the path provided through the agent ID templating feature, which may allow the issuance of an arbitrary SPIFFE ID within the same trust domain, if the attacker controls the value of an EC2 tag prior to attestation, and the attestor is configured for agent ID templating where the tag value is the last element in the path. This issue has been fixed in SPIRE versions 0.11.3 and 0.12.1	Spire
CVE-2021-27098	Mar 05, 2021	In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Servers Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Servers Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.	Spire
CVE-2020-10749	Jun 03, 2020	A vulnerability was found in all versions of containernetworking/plugins before version 0.8.6 A vulnerability was found in all versions of containernetworking/plugins before version 0.8.6, that allows malicious containers in Kubernetes clusters to perform man-in-the-middle (MitM) attacks. A malicious container can exploit this flaw by sending rogue IPv6 router advertisements to the host or other containers, to redirect traffic to the malicious container.	Cni Network Plugins
CVE-2020-11576	Apr 08, 2020	Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing username and 404 otherwise.	Argo Continuous Delivery
CVE-2019-19025	Mar 20, 2020	Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows CSRF in the VMware Harbor Container Registry for the Pivotal Platform.	Harbor
CVE-2019-19026	Mar 20, 2020	Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.	Harbor
CVE-2020-8659	Mar 04, 2020	CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks.	Envoy
CVE-2020-8661	Mar 04, 2020	CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests. CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.	Envoy
CVE-2020-8664	Mar 04, 2020	CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context CNCF Envoy through 1.13.0 has incorrect Access Control when 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.	Envoy
CVE-2019-9946	Apr 02, 2019	Cloud Native Computing Foundation (CNCF) CNI (Container Networking Interface) 0.7.4 has a network firewall misconfiguration Cloud Native Computing Foundation (CNCF) CNI (Container Networking Interface) 0.7.4 has a network firewall misconfiguration which affects Kubernetes. The CNI 'portmap' plugin, used to setup HostPorts for CNI, inserts rules at the front of the iptables nat chains; which take precedence over the KUBE- SERVICES chain. Because of this, the HostPort/portmap rule could match incoming traffic even if there were better fitting, more specific service definition rules like NodePorts later in the chain. The issue is fixed in CNI 0.7.5 and Kubernetes 1.11.9, 1.12.7, 1.13.5, and 1.14.0.	Portmap