CVE-2026-6374

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. the CNA's CVSS baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:tr-cert, epss, ghsa
Trending — 3 sources updated this week
7.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: 7.3Exploit: None knownExposed: 0

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

Use of Hard-coded Credentials vulnerability in Zyxel Networks WAH7601 allows Read Sensitive Constants Within an Executable.

This issue affects WAH7601: through 20.07.2026.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
No patch confirmed yet.
generic

T.C. Siber Güvenlik Başkanlığı

https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0799

Vendor Advisories for CVE-2026-6374(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 49× 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-21 02:48 UTCEG score recompute
  2. 2026-08-21 02:48 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 13:57 UTCEG score recompute
  5. 2026-08-20 13:57 UTCGHSA enrichment
  6. 2026-08-20 09:41 UTCGHSA enrichment
  7. 2026-08-19 20:51 UTCEG score recompute
  8. 2026-08-19 20:51 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 08:00 UTCGHSA enrichment
  11. 2026-08-18 19:10 UTCEG score recompute
  12. 2026-08-18 19:10 UTCGHSA enrichment
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 06:19 UTCGHSA enrichment
  16. 2026-08-17 17:29 UTCEG score recompute
  17. 2026-08-17 17:29 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 04:34 UTCGHSA enrichment
  20. 2026-08-16 15:43 UTCEG score recompute
  21. 2026-08-16 15:43 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:53 UTCEG score recompute
  25. 2026-08-16 02:53 UTCGHSA enrichment
Show 24 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 14:03 UTCEG score recompute
  3. 2026-08-15 14:03 UTCGHSA enrichment
  4. 2026-08-15 01:31 UTCEPSS rescore
  5. 2026-08-15 01:12 UTCGHSA enrichment
  6. 2026-08-14 12:22 UTCGHSA enrichment
  7. 2026-08-13 23:32 UTCEG score recompute
  8. 2026-08-13 23:32 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 10:37 UTCGHSA enrichment
  11. 2026-08-12 21:46 UTCEG score recompute
  12. 2026-08-12 21:46 UTCGHSA enrichment
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-12 08:56 UTCGHSA enrichment
  15. 2026-08-11 20:05 UTCEG score recompute
  16. 2026-08-11 20:05 UTCGHSA enrichment
  17. 2026-08-11 07:14 UTCGHSA enrichment
  18. 2026-08-10 18:24 UTCEG score recompute
  19. 2026-08-10 18:24 UTCGHSA enrichment
  20. 2026-08-10 18:15 UTCEG score recompute
  21. 2026-08-10 18:15 UTCGHSA enrichment
  22. 2026-08-10 13:24 UTCEG score recompute
  23. 2026-08-10 12:17 UTCEG score recompute
  24. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6374?
CVE-2026-6374 is a high vulnerability published on August 10, 2026. Use of Hard-coded Credentials vulnerability in Zyxel Networks WAH7601 allows Read Sensitive Constants Within an Executable. This issue affects WAH7601: through 20.07.2026.
When was CVE-2026-6374 disclosed?
CVE-2026-6374 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6374 actively exploited?
CVE-2026-6374 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 85.8% of all scored CVEs.
What is the CVSS score of CVE-2026-6374?
CVE-2026-6374 has a CVSS v4.0 base score of 7.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-6374?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6374, 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-6374

Explore →

Is Your Infrastructure Affected by CVE-2026-6374?

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

Start Free Scan →Browse All CVEs