Security readout for executives and security teams
Plain-English summary
XX-Net 5.16.6 can mishandle certain WebSocket frames and corrupt application data. The issue is not described as remote code execution or service takeover. Business urgency is moderate: prioritize environments that actually run XX-Net and expose its local WebSocket handling path.
Executive priority
Handle during the next normal remediation cycle unless XX-Net is widely deployed or reachable by untrusted local users. Escalate if business systems depend on data integrity from the affected WebSocket path.
Technical view
The vulnerable WebSocket_receive_worker routine in simple_http_server.py always reads four bytes as a masking key, even when the frame MASK bit is unset. That consumes payload bytes and then decodes remaining data incorrectly. Sources also note missing RSV, opcode, and FIN fragmentation validation.
Likely exposure
Exposure appears limited to XX-Net 5.16.6 deployments using the affected simple_http_server.py WebSocket path. The CVSS vector lists local attack vector, so do not assume internet-wide exposure from the supplied evidence. Version metadata is incomplete beyond the named 5.16.6 release.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not marked CISA KEV. The described impact is low-integrity application data corruption caused by malformed WebSocket frame handling, not confidentiality loss or availability impact in the CVSS data.
Researcher notes
Evidence is strongest for XX-Net 5.16.6 and the linked GitHub fix. The CVE affected-product metadata is incomplete, so confirm exact vulnerable and fixed versions against upstream before closing remediation tickets.
Mitigation direction
- Identify whether XX-Net 5.16.6 is deployed anywhere in scope.
- Review and apply the vendor patch from commit a68b972a where appropriate.
- Track XX-Net release notes for a version containing the fix.
- Restrict access to affected local WebSocket interfaces where feasible.
- Monitor vendor issue and PR threads for corrected version guidance.
Validation and detection
- Inventory installed XX-Net versions and affected hosts.
- Verify simple_http_server.py contains the patched WebSocket parsing logic.
- Confirm no exposed deployment relies on vulnerable 5.16.6 code.
- Check regression tests cover masked and unmasked frame handling.
- Record whether compensating access controls protect the affected interface.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1286: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-10099 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N2.51.4VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
4MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/XX-net/XX-Net/issues/14169CVE reference, VulnCheck · issue-tracking
- https://github.com/XX-net/XX-Net/pull/14170CVE reference, VulnCheck · technical-description
- https://github.com/XX-net/XX-Net/commit/a68b972a84ed6e52df9f30237cf47493b9231b53CVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/xx-net-websocket-frame-parsing-data-corruption-via-simple-http-server-pyCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Syntactic Correctness of Input
Improper Validation of Syntactic Correctness of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.