Cyber Resilience

CVE-2026-26081

Published
20 July 2026
Modified
21 July 2026
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS Score 0.0036 29th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-26081 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Haproxy (inferred from references). Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

HAProxy Community Edition 3.0 through 3.3 before 3.3.3 lacks a length check for the NEW_TOKEN format. HAProxy Enterprise and ALOHA are also affected.

CWE(s)
CWE-130

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

Missing length validation in QUIC NEW_TOKEN handling enables crafted packet exploitation against the public-facing HAProxy service.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-33555Shared CWE-130
CVE-2026-47692Shared CWE-130
CVE-2025-14847Shared CWE-130
CVE-2026-54466Shared CWE-130
CVE-2026-40199Shared CWE-130
CVE-2026-5367Shared CWE-130
CVE-2025-8531Shared CWE-130
CVE-2026-3868Shared CWE-130
CVE-2026-33846Shared CWE-130
CVE-2026-41035Shared CWE-130

Affected Assets

Haproxy
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for handling message lengths and data structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References