Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19773 – Unauthenticated Remote Code Execution – libwebsockets HTTP/2 HPACK Handling (< v5.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19773 is a critical out-of-bounds write vulnerability in libwebsockets, an open-source C library widely embedded in IoT devices, network appliances, and applications to provide WebSocket and HTTP/2 server functionality. The flaw resides in the library’s HTTP/2 HPACK header decompression logic when parsing the :path pseudo-header, and it can be triggered remotely by an unauthenticated attacker sending a specially crafted HTTP/2 request. Successful exploitation can lead to arbitrary code execution in the context of the process using libwebsockets, and the issue has been assigned a CVSS v3.0 base score of 9.8 (Critical).

Technical details

  • Root cause: Insufficient bounds validation in the HPACK header-fragment append routine (lws_frag_append() in lib/roles/h2/hpack.c) allows attacker-controlled data from the :path header to be written past the end of the allocated header-data buffer.
  • Trigger condition: Occurs while a libwebsockets-based server decodes an HTTP/2 request’s compressed headers; no special server configuration is required beyond HTTP/2 support being enabled.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N) — an attacker only needs network reachability to a vulnerable HTTP/2 endpoint.
  • Impact: An out-of-bounds write in this context can corrupt adjacent heap memory, and per the vendor/advisory, can be leveraged to execute arbitrary code in the context of the affected process, fully compromising confidentiality, integrity, and availability of the host process.
  • Disclosure path: Reported to the vendor via Trend Micro’s Zero Day Initiative (ZDI-26-590), credited to researcher Maher Azzouzi.

Affected software

  • libwebsockets — all released versions prior to v5.0.0, including the 4.5.x and 4.4.x branches, that support HTTP/2 server-side HPACK header parsing.
  • The vendor fix was landed on the main branch and is first included in the v5.0.0 tag; earlier maintenance tags (e.g., v4.5.x) do not contain the corrective commit.

Severity

  • CVSS v3.0 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CWE-787: Out-of-bounds Write

Mitigation and recommended actions

  • Immediate: Upgrade libwebsockets to v5.0.0 or later, which includes the bounds check added to the HPACK header-append routine that prevents writes past the allocated max_http_header_data limit.
  • If immediate patching is not possible:
    • Disable or restrict HTTP/2 support on libwebsockets-based servers until the upgrade can be applied, if HTTP/1.1-only operation is acceptable for your deployment.
    • Restrict network exposure of affected services (e.g., place behind a WAF/reverse proxy that can filter or normalize HTTP/2 traffic, or limit access to trusted networks) as a temporary compensating control.
    • Inventory embedded and third-party products that bundle libwebsockets (IoT firmware, network appliances, applications) since the library is frequently vendored, and confirm each is running a version that includes the fix.
    • Monitor for crashes or anomalous process restarts on services using libwebsockets, which could indicate exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge