CVE-2026-74232

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score elevated to 9.8 because this CVE is listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD), indicating that ENISA records real-world exploitation of it. It is not on CISA's Known Exploited Vulnerabilities catalog. A secondary CVSS source baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: ENISA EU KEV (actively exploited, as ENISA records it; Source: ENISA EUVD)
Sources: EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-66999 (ENISA EUVD) · GHSA-jgcj-chrm-4hhc (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictMitigate nowRemediate sooner than your standard update timelines at low mission impact and as soon as possible at medium or high (the SSVC decision on this page).
  • Exploited in the wild, as ENISA's EU KEV records it (Source: ENISA EUVD); CISA has not listed it
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 0.8%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

Zbtlink L3_V2_8 firmware 3.0.0.4.528, Zbtlink WE826-T2 firmware 19.1101, Zbtlink ZBT-7628 firmware 1.0.0.2.007, Zbtlink ZBT-ZBT7621 firmware 1.0.0.3.001, MoreQuick MQAC-7620, MQAC-7620A, MQAP-7620, MQAP-7620A, and MQAP-7628 firmware 1.0.0.2.000, AP522 firmware 1.0.0.2.014, AP7628 and HC5661A firmware 3.0.0.4.380, APG721B firmware 19.0809, HK300 firmware 1.0.0.2.032, and MAP-N10 firmware 1.0.0.2.044 ship a backdoor command-and-control implant (yunmgrd) reachable over an unauthenticated cleartext UDP channel to a hardcoded C2 server. A remote unauthenticated attacker on the network path can hijack the channel and execute arbitrary commands as root. The attacker can also modify DNS entries, exfiltrate PPPoE credentials, and open reverse SSH tunnels.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for an ENISA EU KEV listing (CISA's catalog does not list this CVE): EchelonGraph's rule. Source: ENISA EUVD.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (ENISA EU KEV listing; Source: ENISA EUVD) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). From CISA's SSVC values (Vulnrichment): automatable and technical impact; the others come from the sources named beside them. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
57th
KEV
Not in CISA'sENISA's EU KEV lists it (below). Source: ENISA EUVD

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
ENISA EU KEV (Source: ENISA EUVD)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed August 27, 2026, reported by ENISA; not on CISA's KEV catalog.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (ENISA EU KEV listing; Source: ENISA EUVD) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). From CISA's SSVC values (Vulnrichment): automatable and technical impact; the others come from the sources named beside them. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Oct 31, 2026
No fix on record yet.
Web page

Zbtlink MQWrt yunmgrd Cloud C2 Implant | Advisories | VulnCheck

https://www.vulncheck.com/advisories/zbtlink-mqwrt-yunmgrd-cloud-c2-implant
Web page

Chinese Implants in the Supply Chain | Blog | VulnCheck

http://vulncheck.com/blog/zbt-darklantern-speakingstone

Vendor Advisories for CVE-2026-74232(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 22× in last 7d / 119× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 368 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 268 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 18:23 UTCEG score recompute
  2. 2026-10-30 18:23 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  4. 2026-10-29 17:43 UTCEG score recompute
  5. 2026-10-29 17:43 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-28 17:02 UTCEG score recompute
  8. 2026-10-28 17:02 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  11. 2026-10-27 16:12 UTCEG score recompute
  12. 2026-10-27 16:11 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  14. 2026-10-26 15:21 UTCEG score recompute
  15. 2026-10-26 15:21 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  17. 2026-10-25 13:47 UTCEG score recompute
  18. 2026-10-25 13:47 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2026-66999 · listed August 27, 2026 · reported by ENISA · Source: ENISA EUVD
  20. 2026-10-25 07:33 UTCEG score recompute
  21. 2026-10-25 07:33 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  23. 2026-10-24 06:52 UTCEG score recompute
  24. 2026-10-24 06:51 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
Show 75 more
  1. 2026-10-23 06:10 UTCEG score recompute
  2. 2026-10-23 06:09 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  4. 2026-10-22 05:23 UTCEG score recompute
  5. 2026-10-22 05:23 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-21 04:41 UTCEG score recompute
  8. 2026-10-21 04:41 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-20 03:59 UTCEG score recompute
  11. 2026-10-20 03:59 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-10-19 03:13 UTCEG score recompute
  14. 2026-10-19 03:13 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-18 03:14 UTCEG score recompute
  16. 2026-10-18 02:30 UTCEG score recompute
  17. 2026-10-18 02:30 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-17 01:48 UTCEG score recompute
  20. 2026-10-17 01:48 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  22. 2026-10-16 01:04 UTCEG score recompute
  23. 2026-10-16 01:04 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-14 20:04 UTCEG score recompute
  26. 2026-10-14 20:04 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  28. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  29. 2026-10-13 16:13 UTCEG score recompute
  30. 2026-10-13 16:13 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  32. 2026-10-12 15:32 UTCEG score recompute
  33. 2026-10-12 15:32 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-12 05:40 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-11 19:26 UTCEG score recompute
  36. 2026-10-11 16:41 UTCEG score recompute
  37. 2026-10-11 14:01 UTCEG score recompute
  38. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  39. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  40. 2026-10-10 15:12 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-10 11:01 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-10 06:30 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-10 02:08 UTCEG score recompute
  44. 2026-10-10 02:08 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  46. 2026-10-09 07:19 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-09 03:09 UTCEG score recompute
  48. 2026-10-09 03:09 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  50. 2026-10-08 09:41 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-08 05:31 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-08 01:21 UTCEG score recompute
  53. 2026-10-08 01:21 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  55. 2026-10-07 09:26 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-07 05:16 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-07 01:07 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-06 20:42 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-06 15:57 UTCEG score recompute
  60. 2026-10-06 15:57 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  62. 2026-10-06 11:48 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-06 07:33 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-06 00:54 UTCEG score recompute
  65. 2026-10-06 00:54 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  67. 2026-10-05 17:04 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-05 12:55 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-05 08:45 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-05 04:36 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-04 23:49 UTCEG score recompute
  72. 2026-10-04 23:49 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  74. 2026-10-04 19:39 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-04 14:38 UTCGHSA enrichmentGHSA-jgcj-chrm-4hhc · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-74232?
CVE-2026-74232 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. Zbtlink L3V28 firmware 3.0.0.4.528, Zbtlink WE826-T2 firmware 19.1101, Zbtlink ZBT-7628 firmware 1.0.0.2.007, Zbtlink ZBT-ZBT7621 firmware 1.0.0.3.001, MoreQuick MQAC-7620, MQAC-7620A, MQAP-7620, MQAP-7620A, and MQAP-7628 firmware 1.0.0.2.000, AP522 firmware 1.0.0.2.014, AP7628 and HC5661A firmware…
When was CVE-2026-74232 made public?
CVE-2026-74232 was made public on August 27, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-74232 actively exploited?
CVE-2026-74232 is not currently on CISA's Known Exploited Vulnerabilities catalog. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2026-74232 (added August 27, 2026, reported by ENISA): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74232?
CVE-2026-74232 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74232?
No fix for CVE-2026-74232 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-74232 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-74232?

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