GHSA-qcmw-8mm4-4p28 is a high-severity (CVSS 7.5) CWE-311 vulnerability in antrea.io/antrea. A fix is available for antrea.io/antrea — see the affected versions and patch details below.
Antrea has Missing Encryption of Sensitive Data
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 GHSA-qcmw-8mm4-4p28.
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.
How urgent is this, really
GHSA-qcmw-8mm4-4p28 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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-738bad662b20go get antrea.io/antrea@v1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qcmw-8mm4-4p28 can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-qcmw-8mm4-4p28 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.