CVE-2026-81664
The OpenFaaS gateway registers GET /system/telemetry in …
The OpenFaaS gateway registers GET /system/telemetry in gateway/main.go and, when basic_auth is enabled, wraps each administrative /system/* handler in auth.DecorateWithBasicAuth. TelemetryHandler was left out of that wrap block from 0.27.11, which introduced the route, until 0.27.14, which added it. On an affected gateway the route therefore reaches the forwarding proxy with no credential check and returns whatever the configured provider serves for /system/telemetry, so any client that can reach the gateway port can read the provider's telemetry regardless of the basic_auth setting. The exposed content depends on the provider, and covers resource and invocation metrics for faasd and pod or cluster state for faas-netes.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/geo-chen/oss/blob/main/faas.md
- github.com/openfaas/faas
- github.com/openfaas/faas/blob/0.27.13/gateway/main.go#L216
- github.com/openfaas/faas/commit/8d803bf9e2655aec6a60fd0e25b392839f96af95
- www.vulncheck.com/advisories/openfaas-gateway-0.27.11-through-0.27.13-missing-authenticati
- nvd.nist.gov/vuln/detail/CVE-2026-81664
- cve.org/CVERecord?id=CVE-2026-81664
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.