Kubernetes Ingress Controller Enterprise
Approved changes feed: RSS · Atom
cpe:2.3:a:haproxy:kubernetes_ingress_controller_enterprise:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Haproxy (bcdccbbb-bab3-5a27-b98b-5345a425d85c) |
|---|---|
| Product | Kubernetes Ingress Controller Enterprise (cdfed117-7a4c-5d09-9cb5-3d3c862a5d27) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| 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-110353 |
vulnerable | 2026-11-03 10:16:00.322868 |
Details available
HIGH (7.5)
HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.
Published: 2026-10-22T02:53:33.198Z
Updated: 2026-10-22T19:10:34.428Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.