Missing Authentication for Critical Function Affecting github.com/cloudnativelabs/kube-router/v2/pkg/options package, versions <2.9.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Missing Authentication for Critical Function vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMCLOUDNATIVELABSKUBEROUTERV2PKGOPTIONS-16778747
- published20 May 2026
- disclosed6 May 2026
- creditoffset
Introduced: 6 May 2026
CVE NOT AVAILABLE CWE-306 Â (opens in a new tab)How to fix?
Upgrade github.com/cloudnativelabs/kube-router/v2/pkg/options to version 2.9.0 or higher.
Overview
Affected versions of this package are vulnerable to Missing Authentication for Critical Function in the gRPC management server. An attacker can access sensitive BGP configuration and manipulate routing decisions by sending unauthorized gRPC requests from any pod within the cluster. This includes injecting arbitrary BGP routes, enumerating peer configurations, adding or removing BGP neighbors, and modifying routing policies, all without authentication or encryption. This is only exploitable if the routing controller is started with --run-router and the default admin port is exposed on the node's primary IP.
Workaround
This vulnerability can be mitigated by setting --gobgp-admin-port=0 to disable the gRPC server, adding host-level iptables INPUT rules to block port 50051 from non-localhost sources, or applying Kubernetes NetworkPolicy (noting that NodePort/host-network traffic may bypass NetworkPolicy in some CNI implementations).