OpenFaaS Gateway 0.27.11 through 0.27.13 Missing Authentication on the /system/telemetry Route
Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.
cve-program · CVE-2026-81664
PublishedThe 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-81664 · CVE overview and exploitation status
cve-program · CVE-2026-81664
- https://github.com/geo-chen/oss/blob/main/faas.md
- https://github.com/openfaas/faas
- https://github.com/openfaas/faas/commit/8d803bf9e2655aec6a60fd0e25b392839f96af95
- https://github.com/openfaas/faas/blob/0.27.13/gateway/main.go#L216
- https://www.vulncheck.com/advisories/openfaas-gateway-0.27.11-through-0.27.13-missing-authentication-on-the-system-telemetry-route
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.