CVE-2026-34635

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

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

is affected by a Use of Hard-coded Cryptographic Key vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and write access. Exploitation of this issue does not require user interaction. Scope is changed.

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

Published

August 11, 2026

Last Modified

August 13, 2026

References (1)

Vendor Advisories for CVE-2026-34635(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 / 47× 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 01:23 UTCEG score recompute
  2. 2026-08-21 01:23 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 14:22 UTCGHSA enrichment
  5. 2026-08-20 03:21 UTCEG score recompute
  6. 2026-08-20 03:21 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 16:20 UTCGHSA enrichment
  9. 2026-08-19 05:19 UTCGHSA enrichment
  10. 2026-08-18 18:16 UTCEG score recompute
  11. 2026-08-18 18:16 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 07:15 UTCGHSA enrichment
  14. 2026-08-17 20:14 UTCEG score recompute
  15. 2026-08-17 20:14 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 09:13 UTCGHSA enrichment
  18. 2026-08-16 22:13 UTCEG score recompute
  19. 2026-08-16 22:13 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:11 UTCEG score recompute
  22. 2026-08-16 11:11 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-16 00:11 UTCGHSA enrichment
  25. 2026-08-15 13:10 UTCGHSA enrichment
Show 22 more
  1. 2026-08-15 02:09 UTCEG score recompute
  2. 2026-08-15 02:09 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 15:09 UTCGHSA enrichment
  5. 2026-08-14 04:08 UTCEG score recompute
  6. 2026-08-14 04:08 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 17:07 UTCGHSA enrichment
  9. 2026-08-13 08:22 UTCGHSA enrichment
  10. 2026-08-12 21:22 UTCGHSA enrichment
  11. 2026-08-12 17:36 UTCEG score recompute
  12. 2026-08-12 17:36 UTCGHSA enrichment
  13. 2026-08-12 17:07 UTCEG score recompute
  14. 2026-08-12 17:07 UTCGHSA enrichment
  15. 2026-08-12 16:41 UTCEG score recompute
  16. 2026-08-12 16:41 UTCGHSA enrichment
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-12 05:40 UTCGHSA enrichment
  19. 2026-08-11 18:39 UTCEG score recompute
  20. 2026-08-11 18:39 UTCGHSA enrichment
  21. 2026-08-11 16:46 UTCEG score recompute
  22. 2026-08-11 16:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-34635?
CVE-2026-34635 is a high vulnerability published on August 11, 2026. is affected by a Use of Hard-coded Cryptographic Key vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and write access. Exploitation of this issue does not require user…
When was CVE-2026-34635 disclosed?
CVE-2026-34635 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34635 actively exploited?
CVE-2026-34635 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 90.9% of all scored CVEs.
What is the CVSS score of CVE-2026-34635?
CVE-2026-34635 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-34635?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34635, 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-34635

Explore →

Is Your Infrastructure Affected by CVE-2026-34635?

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

Start Free Scan →Browse All CVEs