GHSA-qcmw-8mm4-4p28
HIGHGHSA-qcmw-8mm4-4p28 is a high-severity (CVSS 7.5) CWE-311 vulnerability in antrea.io/antrea. O3 Security confirms whether GHSA-qcmw-8mm4-4p28 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Antrea has Missing Encryption of Sensitive Data
Blast Radius
antrea.io/antrea🐹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
This is a missing encryption vulnerability (CWE-311) affecting inter-Node Pod traffic. In Antrea clusters configured for dual-stack networking with IPsec encryption enabled (trafficEncryptionMode: ipsec), Antrea fails to apply encryption for IPv6 Pod traffic.
While the IPv4 traffic is correctly encrypted via ESP (Encapsulating Security Payload), traffic using IPv6 is transmitted in plaintext. This occurs because the packets are encapsulated (using Geneve or VXLAN) but bypass the IPsec encryption layer.
Impacted Users: users with dual-stack clusters and IPsec encryption enabled.
Single-stack IPv4 or IPv6 clusters are not affected.
Patches
Yes, the issue has been patched: https://github.com/antrea-io/antrea/pull/7759 Users should upgrade to one of the following versions:
- Antrea v2.6.0 or later
- Antrea v2.5.2
- Antrea v2.4.5
Antrea recommends running the antctl check installation --run ipsec tool after upgrading to verify that both address families are correctly producing ESP traffic.
Workarounds
There is no configuration workaround to enable IPsec IPv6 in affected versions. If an immediate upgrade is not possible, user may consider using WireGuard instead for inter-Node Pod traffic encryption. The WireGuard support in Antrea does not suffer from the same issue.
Resources
Pull Request with Fix: antrea-io/antrea#7759 Validation Tool PR: antrea-io/antrea#7757 Antrea Documentation: Traffic Encryption Guide
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | antrea.io/antrea | ≥ 1.11.0 | No fix |
| 🐹Go | antrea.io/antrea | ≥ 2.5.0 | No fix |
| 🐹Go | antrea.io/antrea | all versions | 1.11.0-alpha.0.0.20260225185322-738bad662b20 |
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
No patched version of antrea.io/antrea has shipped for GHSA-qcmw-8mm4-4p28 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-qcmw-8mm4-4p28 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-qcmw-8mm4-4p28. 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-qcmw-8mm4-4p28 in your dependencies?
O3 detects GHSA-qcmw-8mm4-4p28 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.