CVE-2026-51106

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue in TokTok qTox v1.18.4 allows a local attacker to cause a denial of service via the src/persistence/serialize.cpp component

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
58(Track*)
EG Risk 58/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

[Bug]: SettingsSerializer `readStream()` Unbounded Allocation and Integer Overflow · Issue #706 · TokTok/qTox · GitHub

https://github.com/TokTok/qTox/issues/706

Vendor Advisories for CVE-2026-51106(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-29 03:51 UTCGHSA enrichment
  2. 2026-08-29 00:00 UTCEG score recompute
  3. 2026-08-28 23:59 UTCGHSA enrichment
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 16:05 UTCGHSA enrichment
  6. 2026-08-28 11:53 UTCGHSA enrichment
  7. 2026-08-28 08:03 UTCGHSA enrichment
  8. 2026-08-28 04:10 UTCGHSA enrichment
  9. 2026-08-28 00:21 UTCEG score recompute
  10. 2026-08-28 00:20 UTCGHSA enrichment
  11. 2026-08-27 20:28 UTCEG score recompute
  12. 2026-08-27 20:28 UTCGHSA enrichment
  13. 2026-08-27 20:16 UTCEG score recompute▲ 9.30
  14. 2026-08-27 20:16 UTCGHSA enrichment
  15. 2026-08-27 20:13 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 19:22 UTCNVD update
  18. 2026-08-26 18:41 UTCEG score recompute
  19. 2026-08-26 18:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-51106?
CVE-2026-51106 is a critical vulnerability published on August 26, 2026. An issue in TokTok qTox v1.18.4 allows a local attacker to cause a denial of service via the src/persistence/serialize.cpp component
When was CVE-2026-51106 disclosed?
CVE-2026-51106 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-51106 actively exploited?
CVE-2026-51106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.8% of all scored CVEs.
What is the CVSS score of CVE-2026-51106?
CVE-2026-51106 has a CVSS v3.1 base score of 9.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-51106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-51106, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-51106

Explore →

Is Your Infrastructure Affected by CVE-2026-51106?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs