Mongoose validation bypass in WebSocket frame handling
- Exploited
- No known exploitation
- Fix
- Fixed in 7.24
- Who is exposed
- Not reported
Summary
Mongoose, a web server and networking library, has a WebSocket frame validation flaw. A remote attacker, without logging in, can send one malformed continuation frame so the application receives a message with attacker-chosen flags and data cut short by one byte, while the connection stays open and no user action is needed.
Written by a model
Original description
Mongoose Embedded Web Server / Networking Library before 7.24 contains a WebSocket fragmentation validation vulnerability that allows remote attackers to spoof message metadata by sending a single CONTINUATION frame with FIN=1 as the first data frame instead of a required TEXT/BINARY start frame, violating RFC 6455 sequencing rules. Attackers can craft this malformed frame to make mg_ws_cb() in src/ws.c misinterpret the first byte of payload as saved FIN/opcode flags, causing the application to receive a dispatched MG_EV_WS_MSG event with attacker-controlled flags and data truncated by one byte without closing the connection.
What to do
Upgrade to a fixed version: 7.24.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-106024 (Mongoose before 7.24 WebSocket Frame Validation Bypass via ws.c), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-106024 (entry last updated 2026-11-20):
Affected:
- cesanta mongoose: fixed in 7.24
Fixed versions: 7.24.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-106024 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106024 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cesanta/mongoose/releases/tag/7.24
- https://www.vulncheck.com/advisories/mongoose-before-websocket-frame-validation-bypass-via-ws-c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-106024
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-106024"}.Affected versions
- cesanta mongoosefixed in 7.24
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Exploit | GitHub · cesanta/mongoose · Advisory GHSA-8r69-8vm6-fv67 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-106024 |
| Record | NVD · CVE-2026-106024 |
| Other links 2 | |
| Patch | GitHub · cesanta/mongoose · Release 7.24 |
| Link | vulncheck.com · advisories/mongoose-before-websocket-frame-validation-bypass-via-ws-c |
Questions about CVE-2026-106024
Is CVE-2026-106024 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-106024?
mongoose: before 7.24.
Source: cve.now feed data
How do I fix CVE-2026-106024?
Upgrade to a fixed version: 7.24.
Source: cve.now feed data
Related
- CVE-2026-73251Mongoose Built-in TLS: CA-bundle certificate chain accepted without any signature verification
- CVE-2026-73253Mongoose: TLS Hostname Verification Bypass via Overly Permissive Wildcard Matching
- CVE-2026-73256Mongoose: HTTP/1.0 detection off-by-one enables request smuggling via chunked TE
- CVE-2026-73257Mongoose: Content-Length + Transfer-Encoding coexistence enables request smuggling
- CVE-2026-63626Mongoose: ppp_handle_ipv6cp() uses attacker-controlled length without bounds check — OOB read and heap overflow (PPP/PPPoE, MG_ENABLE_IPV6)
- CVE-2026-11404Cesanta Mongoose Out-of-Bounds Read in MG_TLS_BUILTIN ClientHello Session ID Parsing
No corrections so far. Something wrong on this page? Report an error.