chore(deps): update module github.com/containernetworking/plugins to v1.9.0 [security] #6591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.8.0->v1.9.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2025-67499
Background
The CNI
portmapplugin 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 to198.51.100.42:53be forwarded to the container's network.Vulnerability
When the
portmapplugin is configured with thenftablesbackend, 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
portmapplugin be explicitly configured to use thenftablesbackend. (Theiptablesbackend is the default.)Patches
This is fixed as of CNI plugins v1.9.0
Workarounds
Configure the
portmapplugin to use theiptablesbackend. It does not have this vulnerability.Release Notes
containernetworking/plugins (github.com/containernetworking/plugins)
v1.9.0: CNI plugins v1.9.0Compare Source
What's Changed
This release fixes CVE-2025-67499, a bug in the
nftablesbackend for theportmapplugin that can cause traffic to be unexpectedly intercepted.Bugs
Other changes
Full Changelog: containernetworking/plugins@v1.8.0...v1.9.0
Configuration
📅 Schedule: Branch creation - "" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.