VulnSocial

CVE-2026-26081Patch(haproxy / aloha)

LOWCVSS 4.8 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch haproxy aloha systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

haproxy CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Patch / fix
Other references
Weakness type (CWE)
CWE-130

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • aloha
  • haproxy
  • haproxy_enterprise

Threat summary

  • Patch or workaround signal is available
  • 4 mentions across 4 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 4 signals
  • Technical details provided in 4 signals
  • Disclosure: 1 classified signal
  • Peaked 3d ago at 1 mentions (2026-02-12); latest day: 1
  • 4 total mentions across 4 days

Affected systems

Vendors
haproxy
Products
alohahaproxyhaproxy_enterprise

3 versions affected across 3 products

Deep dive

Activity timeline4 mentions / 4d
00111Mentions · 2026-02-12: 1Mentions · 2026-02-15: 1Mentions · 2026-02-28: 1Mentions · 2026-08-28: 1Patch / Workaround · 2026-02-12: 1Patch / Workaround · 2026-02-15: 1Patch / Workaround · 2026-02-28: 1Patch / Workaround · 2026-08-28: 1Technical Details · 2026-02-12: 1Technical Details · 2026-02-15: 1Technical Details · 2026-02-28: 1Technical Details · 2026-08-28: 102-1202-1502-2808-28
Signal classification2 categories
Patch
375.0%
Disclosure
125.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-02-121
Patch1
2026-02-151
Patch1
2026-02-281
Disclosure1
2026-08-281
Patch1
Full discourse4 posts
  • tetsuo@tetsuoai
    Disclosure

    Proud to have discovered two QUIC-related issues in HAProxy that led to CVE-2026-26080 & CVE-2026-26081 (DoS crashes via malformed packets). Thanks to willyt for the credit in the 3.1.15 release announcement!

    Post summary

    Two QUIC-related DoS vulnerabilities (CVE-2026-26080 & CVE-2026-26081) were discovered in HAProxy and addressed in the 3.1.15 release announcement.

    161621412216.8K
    231.3K followersView on X
  • 𝔸𝕟𝕠𝕟𝕪𝕞𝕠𝕦𝕤 ℍ𝕒𝕔𝕜𝕥𝕚𝕧𝕚𝕤𝕥☭⃠🅇@YourAnon_irc
    Patch

    Recent ServiceNow flaws (CVSS 10.0) allow unauthenticated RCE/SQLi, threatening data privacy & integrity in transit. Patch immediately! Also, HAProxy QUIC vulnerabilities (CVE-2026-26081, CVE-2026-26080) fixed to prevent crashes. #Cybersecurity #News #Vulnerabilities

    Post summary

    The message highlights critical ServiceNow RCE/SQLi flaws (CVSS 10.0) and recent HAProxy QUIC vulnerabilities, urging immediate patching to prevent data privacy and crash risks.

    0000065
    17 followersView on X
  • Autumn Good@autumn_good_35
    Patch

    『If you use an affected product with the QUIC component enabled, you should update to a fixed version as soon as possible.』 HAProxy February 2026 — CVE-2026-26080 and CVE-2026-26081: QUIC denial of service https://www.haproxy.com/blog/cves-2026-quic-denial-of-service

    Post summary

    HAProxy’s blog post alerts that CVE‑2026‑26080 and CVE‑2026‑26081 cause a QUIC denial‑of‑service; users should upgrade to the patched version immediately.

    00000650
    6.7K followersView on X
  • Ferramentas Linux@Cezar_H_Linux
    Patch

    #Debian DSA-6130-1 is out. HAProxy + QUIC = potential instant crash. Here is exactly what CVE-2026-26081 does and how to fix it without breaking your SLOs. 🧵 Read more: 👉 https://tinyurl.com/4s6uptr7 #Security https://t.co/VOJz6zFs8T

    Post summary

    Debian’s DSA‑6130‑1 addresses CVE‑2026‑26081, a crash in HAProxy when using QUIC, and offers a fix that preserves service level objectives.

    0000065
    1.3K followersView on X
CPE platform detail83 entries

83 of 83 entries

PartVendorProductVersionTarget SWTarget HW
Apphaproxyaloha---
Apphaproxyhaproxy---
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.0r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.1r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--
Apphaproxyhaproxy_enterprise3.2r1--

Explore more

Back to dashboardhaproxy CVEsaloha vulnerabilities