Approved changes feed: RSS · Atom
cpe:2.3:a:linuxfoundation:antrea:*:*:*:*:*:kubernetes:*:*
part: a version: * update: *
| Vendor | Linuxfoundation (4b459c90-8cdb-5268-beb4-b69b5fe74234) |
|---|---|
| Product | Antrea (b83ec4fd-bcfa-5d15-9c0c-513adbe915ec) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | kubernetes |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-34992 |
vulnerable | 2026-06-08 07:59:13.403941 |
Missing Encryption of Sensitive Data in antrea.io/antrea
Antrea is a Kubernetes networking solution intended to be Kubernetes native. Prior to 2.4.5 and 2.5.2, a missing encryption vulnerability affects 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. This vulnerability is fixed in 2.4.5 and 2.5.2.
Published: 2026-04-06T16:31:39.224Z
Updated: 2026-04-07T14:10:53.588Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-25804 |
vulnerable | 2026-06-08 07:53:20.502028 |
Antrea has invalid enforcement order for network policy rules caused by integer overflow
Antrea is a Kubernetes networking solution intended to be Kubernetes native. Prior to versions 2.3.2 and 2.4.3, 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. This issue has been patched in versions 2.4.3.
Published: 2026-02-06T22:58:35.041Z
Updated: 2026-02-09T15:25:44.301Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.