# CVE-2025-67499: plugins — Fixed in 1.9.0 🐹 🐹 Go Not in CISA KEV MEDIUM severity # CVE-2025-67499 — plugins MEDIUM [Fix: containernetworking/plugins#1210](https://github.com/containernetworking/plugins/pull/1210) CVE-2025-67499 is a medium-severity (CVSS 6.6) Information Exposure vulnerability in github.com/containernetworking/plugins. A fix is available for github.com/containernetworking/plugins — see the affected versions and patch details below. CNI Plugins Portmap nftables backend intercepts non-local traffic Also known as[GHSA-jv3w-x3r3-g6rm](/vulnerability/GHSA-jv3w-x3r3-g6rm)GO-2025-4222 Published Dec 9, 2025 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67499. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.1%probability of exploitation in next 30 days Lower Risk+0.01% Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk 0.00%0.22%0.43%0.65%0.0%0.1%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected 🐹`github.com/containernetworking/plugins` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems. ## Description #### Background The CNI `portmap` plugin allows containers to emulate opening a host port, forwarding that traffic to the container. For example, if a host has the IP 198.51.100.42, a container may request that all packets to `198.51.100.42:53` be forwarded to the container's network. #### Vulnerability When the `portmap` plugin is configured with the `nftables` backend, it inadvertently forwards all traffic with the same destination port as the host port, **ignoring the destination IP**. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. In the given example above, traffic destined to port 53 but for a _separate container_ would still be captured and forwarded, even though it was not destined for the host. #### Impact Containers (i.e. kubernetes pods) 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. (The `iptables` backend is the default.) #### Patches This is fixed as of CNI plugins v1.9.0 #### Workarounds Configure the `portmap` plugin to use the `iptables` backend. It does not have this vulnerability. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐹Go `github.com/containernetworking/plugins` ≥ 1.6.0&&< 1.9.0 1.9.0`go get github.com/containernetworking/plugins@v1.9.0` ## Affected Products 1 product · 1 configurations Application `cni network plugins`linuxfoundation ≥ 1.6.0 && < 1.9.0 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containernetworking/plugins, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update github.com/containernetworking/plugins to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67499 is resolved across your whole dependency graph. 3. ### Workarounds Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatModerate This vulnerability is rated Moderate for Red Hat because it allows containers to intercept non-local traffic when the CNI portmap plugin is explicitly configured to use the \`nftables\` backend. This issue affects CNI portmap plugin versions 1.6.0 through 1.8.0. Red Hat products are only affected if the \`nftables\`… Workaround published by Red Hat > Configure the CNI portmap plugin to use the \`iptables\` backend instead of \`nftables\`. This can typically be achieved by modifying the CNI network configuration. After making this configuration change, services utilizing the CNI portmap plugin may require a restart or reload for the changes to take effect. Source: [Red Hat security advisory for CVE-2025-67499](https://access.redhat.com/security/cve/cve-2025-67499) (CC BY 4.0) ## Frequently Asked Questions \### Background The CNI \`portmap\` plugin allows containers to emulate opening a host port, forwarding that traffic to the container. For example, if a host has the IP 198.51.100.42, a container may request that all packets to \`198.51.100.42:53\` be forwarded to the container's network. ### Vulnerability When the \`portmap\` plugin is configured with the \`nftables\` backend, it inadvertently forwards all traffic with the same destination port as the host port, \*\*ignoring the destination IP\*\*. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. I O3 Security · Impact-Aware SCA ### Is CVE-2025-67499 in your dependencies? Find it across Go, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)