Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
haproxy-quic-cves-2026 — Reproducible lab and network PoCs for HAProxy QUIC CVE-2026-26080 and CVE-2026-26081 | Kitploit
Tools/GitHubGitHub/zeerg/haproxy-quic-cves-2026
Packet Sniffing & AnalysisContainer SecurityVulnerability AnalysisFuzzingNetwork SecurityLabs & Practice
GitHubzeerg/haproxy-quic-cves-2026

haproxy-quic-cves-2026

Reproducible lab and network PoCs for HAProxy QUIC CVE-2026-26080 and CVE-2026-26081

View Repository
20 days agoNot yet reviewed
Share

Isolated reproduction lab

Scope

This lab compares official HAProxy 3.2.11 and 3.2.12 images for two QUIC denial-of-service vulnerabilities. It sends one packet per control, waits for a bounded observation period, checks exact evidence, and removes all target containers.

The packet builders only send to 127.0.0.1. The sender joins the target's Docker network namespace, which has no external interface.

Requirements

  • Docker with Linux containers.
  • Python 3.10 or later.
  • Network access to pull the three digest-pinned base images and Python packages.

Run

Run from the repository root:

python3 lab/verify.py

The verifier runs the vulnerable and fixed controls sequentially for each CVE. It does not expose a QUIC port on the host.

Evidence gates

CaseRequired evidence
CVE-2026-26080 vulnerableExit 134, at least 20 qc_parse_frm() enter events, at least 20 leave events, and the master exit report
CVE-2026-26080 fixedProcess remains live and logs malformed frame type
CVE-2026-26081 vulnerableExit 139 plus quic_token_check, Segmentation fault, and the master exit report
CVE-2026-26081 fixedProcess remains live and logs invalid token length

A timeout, unrelated exit, missing marker, or cleanup failure fails the run. See ../docs/EVIDENCE.md for the dated observations.

Topology

PoC container
  `--network container:<fixed target name>`
                 |
                 | UDP 127.0.0.1:8443
                 v
HAProxy target container
  `--network none`
  no published ports
  bounded CPU, memory, and process count

Files

PathPurpose
verify.pyBuilds the sender, runs all four controls, checks evidence, and confirms cleanup
poc_cve_2026_26080.pyBuilds and protects the truncated-frame-type QUIC Initial
poc_cve_2026_26081.pyBuilds the short-token QUIC Initial
haproxy.cfgMinimal QUIC listener with developer-level QUIC tracing
start-haproxy-lab.shCreates a one-day self-signed certificate and starts HAProxy
Dockerfile.pocBuilds the digest-pinned Python sender image
Dockerfile.sourceBuilds a selected vendored HAProxy release with OpenSSL QUIC compatibility

Local source builds

The local builds are secondary controls. The official AWS-LC images in verify.py are authoritative for runtime comparison.

docker build -f lab/Dockerfile.source \
  --build-arg VERSION=3.2.11 \
  -t haproxy-quic-local:3.2.11 .

docker build -f lab/Dockerfile.source \
  --build-arg VERSION=3.2.12 \
  -t haproxy-quic-local:3.2.12 .

The Dockerfile verifies the selected source archive against its tracked SHA-256 sidecar before extraction.

Standalone packet options

Both packet builders accept --port and --receive. The token PoC also accepts --token-length and --sweep. The destination address is fixed to loopback.

python3 lab/poc_cve_2026_26080.py --port 18443 --receive
python3 lab/poc_cve_2026_26081.py --port 18443 --token-length 1 --receive

These commands require a local authorized QUIC listener. The full verifier is the supported release test.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →