Information Exposure Affecting rke2-runtime-1.32 package, versions <1.32.10.2.1-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (4th percentile)

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 applications

Snyk Learn

Learn about Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-RKE2RUNTIME132-14421834
  • published15 Dec 2025
  • disclosed10 Dec 2025

Introduced: 10 Dec 2025

CVE-2025-67499  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Chainguard rke2-runtime-1.32 to version 1.32.10.2.1-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rke2-runtime-1.32 package and not the rke2-runtime-1.32 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.

CVSS Base Scores

version 3.1