GHSA-QCMW-8MM4-4P28

Vulnerability from github – Published: 2026-04-03 04:02 – Updated: 2026-04-06 23:40
VLAI?
Summary
Antrea has Missing Encryption of Sensitive Data
Details

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

Severity ?
7.1 (High)
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c 2.4.5"
      },
      "package": {
        "ecosystem": "Go",
        "name": "antrea.io/antrea"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.11.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c 2.5.2"
      },
      "package": {
        "ecosystem": "Go",
        "name": "antrea.io/antrea"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.5.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "antrea.io/antrea"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.11.0-alpha.0.0.20260225185322-738bad662b20"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34992"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-311"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-03T04:02:47Z",
    "nvd_published_at": "2026-04-06T17:17:12Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nThis 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.\n\nWhile 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.\n\nImpacted Users: users with dual-stack clusters and IPsec encryption enabled.\n\nSingle-stack IPv4 or IPv6 clusters are not affected.\n\n### Patches\nYes, the issue has been patched: https://github.com/antrea-io/antrea/pull/7759\nUsers should upgrade to one of the following versions:\n* Antrea v2.6.0 or later\n* Antrea v2.5.2\n* Antrea v2.4.5\n\nAntrea recommends running the `antctl check installation --run ipsec` tool after upgrading to verify that both address families are correctly producing ESP traffic.\n\n### Workarounds\nThere 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.\n\n### Resources\nPull Request with Fix: [antrea-io/antrea#7759](https://github.com/antrea-io/antrea/pull/7759)\nValidation Tool PR: [antrea-io/antrea#7757](https://github.com/antrea-io/antrea/pull/7757)\nAntrea Documentation: [Traffic Encryption Guide](https://github.com/antrea-io/antrea/blob/main/docs/traffic-encryption.md)",
  "id": "GHSA-qcmw-8mm4-4p28",
  "modified": "2026-04-06T23:40:30Z",
  "published": "2026-04-03T04:02:47Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/antrea-io/antrea/security/advisories/GHSA-qcmw-8mm4-4p28"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34992"
    },
    {
      "type": "WEB",
      "url": "https://github.com/antrea-io/antrea/pull/7757"
    },
    {
      "type": "WEB",
      "url": "https://github.com/antrea-io/antrea/pull/7759"
    },
    {
      "type": "WEB",
      "url": "https://github.com/antrea-io/antrea/commit/738bad662b20a5d358d19466936176ef580a9b07"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/antrea-io/antrea"
    },
    {
      "type": "WEB",
      "url": "https://github.com/antrea-io/antrea/blob/main/docs/traffic-encryption.md"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Antrea has Missing Encryption of Sensitive Data"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.