How severe is CVE-2026-34992?

No CVSS score has been assigned to CVE-2026-34992 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-34992?

CVE-2026-34992 affects the following packages: antrea.io/antrea (Go), antrea.io/antrea (Go), antrea.io/antrea (Go). Ecosystems affected: Go.

How do I fix CVE-2026-34992?

A fix is available for CVE-2026-34992; check the affected-versions list above or the advisory for the patched release of antrea.io/antrea, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2026-34992 in my Go dependencies?

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.

How do I mitigate CVE-2026-34992 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-34992 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-34992 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-34992?

CVE-2026-34992 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 2th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-34992?

CVE-2026-34992 is classified as CWE-311 (CWE-311). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-34992 published, and has it been updated?

CVE-2026-34992 was published on April 6, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-34992 — antrea

Fix: antrea-io/antrea@738bad6

CVE-2026-34992 is a CWE-311 vulnerability in antrea.io/antrea. A fix is available for antrea.io/antrea — see the affected versions and patch details below.

Missing Encryption of Sensitive Data in antrea.io/antrea

Also known asGHSA-qcmw-8mm4-4p28GO-2026-5579

Published

Apr 6, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-34992.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs2th percentile — riskier than 2% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐹antrea.io/antrea🐹antrea.io/antrea🐹antrea.io/antrea

Real-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

3 total 1 fixed

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`go get antrea.io/antrea@v1.11.0-alpha.0.0.20260225185322-738bad662b20`

Affected Products

1 product · 2 configurations

Application

antrealinuxfoundation

≥ 2.5.0 && < 2.5.2

range

Detection & mitigation playbook

Open-source dependency

Detect
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
A fix is available for CVE-2026-34992; check the affected-versions list above or the advisory for the patched release of antrea.io/antrea, then make sure no transitive dependency still pins the vulnerable range.
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.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is CVE-2026-34992 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works