GHSA-86x4-wp9f-wrr9
Antrea has invalid enforcement order for network policy rules caused by integer overflow
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
antrea.io/antrea🐹antrea.io/antreaReal-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
Impact
Antrea's network policy priority assignment system has a uint16 arithmetic overflow bug that causes incorrect OpenFlow priority calculations when handling a large numbers of policies with various priority values. This results in potentially incorrect traffic enforcement.
If a user creates a large number of Antrea NetworkPolicies (ANP or ACNP) with varying priorities, some rules with lower logical priorities (higher numerical priority values) may take precedence over rules with higher logical priorities (lower numerical priority values). Traffic that should be denied by the configured Antrea NetworkPolicies may end up being allowed, potentially letting an attacker access a sensitive service. Traffic that should be allowed by the configured Antrea NetworkPolicies may end up being denied, breaking applications and potentially opening the door for denial-of-service attacks.
The Antrea NetworkPolicy system comes with support for priority Tiers. Rules defined within a Tier cannot take precedence over rules defined in higher priority Tiers. Some users / roles may only be authorized to define within specific Tiers. This security vulnerability enables such users to intentionally "escape" their Tier and override rules in higher priority Tiers.
Antrea deployments that only use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.
Patches
https://github.com/antrea-io/antrea/pull/7496 Antrea v2.5.0 Antrea v2.4.3 Antrea v2.3.2
Workarounds
Antrea deployments that only use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.
For users leveraging Antrea NetworkPolicies, there is no way to fix or remediate the vulnerability without upgrading.
Resources
https://gist.github.com/antoninbas/c429cc3e5bb8479ba7ff38fd6fde59d9 https://github.com/antrea-io/antrea/pull/7496 https://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.md
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | antrea.io/antrea | all versions | 2.3.2 |
| 🐹Go | antrea.io/antrea | ≥ 2.4.0&&< 2.4.3 | 2.4.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for antrea.io/antrea. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update antrea.io/antrea to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86x4-wp9f-wrr9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-86x4-wp9f-wrr9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-86x4-wp9f-wrr9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-86x4-wp9f-wrr9 in your dependencies?
O3 detects GHSA-86x4-wp9f-wrr9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.