CNA Plugins Portmap nftables backend can intercept non-local traffic

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.6 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

EPSS

• CVE-2025-67499: 0.14% estimated exploitation activity in the next 30 days; percentile 3.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

9 Dec 2025, 17:18 UTC

Last modified by the source

24 Mar 2026, 21:05 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jv3w-x3r3-g6rm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67499

Advisory: CNA Plugins Portmap nftables backend can intercept non-local traffic
IDs: CVE-2025-67499, GHSA-jv3w-x3r3-g6rm
Record: https://patchnext.com/advisories/cve-2025-67499 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/containernetworking/plugins 1.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/containernetworking/plugins: affected >= 1.6.0, < 1.9.0; fixed in 1.9.0

## Suggested inspection (read-only)
- Go github.com/containernetworking/plugins: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/containernetworking/plugins.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jv3w-x3r3-g6rm (GitHub-reviewed advisory GHSA-jv3w-x3r3-g6rm lists affected ranges: Go github.com/containernetworking/plugins >=1.6.0 <1.9.0)

Commands are suggestions: review each one before running it.