CVE-2026-61753

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

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

NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

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

Published

September 1, 2026

Last Modified

September 2, 2026

Advisory Details (1)

Auto-updated Sep 1, 2026
No patch confirmed yet.
generic
https://www.cve.org/CVERecord?id=CVE-2026-61753

Vendor Advisories for CVE-2026-61753(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 26× in last 7d / 77× 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-09-21 06:36 UTCEG score recompute
  2. 2026-09-21 06:36 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 18:55 UTCGHSA enrichment
  5. 2026-09-20 07:14 UTCGHSA enrichment
  6. 2026-09-19 19:28 UTCEG score recompute
  7. 2026-09-19 19:28 UTCGHSA enrichment
  8. 2026-09-19 07:47 UTCGHSA enrichment
  9. 2026-09-18 20:07 UTCEG score recompute
  10. 2026-09-18 20:06 UTCGHSA enrichment
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 08:25 UTCGHSA enrichment
  13. 2026-09-17 20:45 UTCEG score recompute
  14. 2026-09-17 20:45 UTCGHSA enrichment
  15. 2026-09-17 09:04 UTCGHSA enrichment
  16. 2026-09-16 21:22 UTCEG score recompute
  17. 2026-09-16 21:22 UTCGHSA enrichment
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 09:06 UTCEG score recompute
  20. 2026-09-16 09:06 UTCGHSA enrichment
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 21:04 UTCGHSA enrichment
  23. 2026-09-15 09:24 UTCEG score recompute
  24. 2026-09-15 09:24 UTCGHSA enrichment
  25. 2026-09-14 21:43 UTCGHSA enrichment
Show 52 more
  1. 2026-09-14 10:02 UTCGHSA enrichment
  2. 2026-09-13 22:12 UTCEG score recompute
  3. 2026-09-13 22:12 UTCGHSA enrichment
  4. 2026-09-13 10:30 UTCGHSA enrichment
  5. 2026-09-12 22:49 UTCEG score recompute
  6. 2026-09-12 22:49 UTCGHSA enrichment
  7. 2026-09-12 11:08 UTCGHSA enrichment
  8. 2026-09-11 23:18 UTCEG score recompute
  9. 2026-09-11 23:18 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 10:57 UTCEG score recompute
  12. 2026-09-11 10:57 UTCGHSA enrichment
  13. 2026-09-11 09:37 UTCEPSS rescore
  14. 2026-09-10 23:16 UTCGHSA enrichment
  15. 2026-09-10 11:36 UTCEG score recompute
  16. 2026-09-10 11:36 UTCGHSA enrichment
  17. 2026-09-09 23:37 UTCGHSA enrichment
  18. 2026-09-09 11:03 UTCGHSA enrichment
  19. 2026-09-08 23:22 UTCEG score recompute
  20. 2026-09-08 23:22 UTCGHSA enrichment
  21. 2026-09-08 22:01 UTCEPSS rescore
  22. 2026-09-08 10:01 UTCGHSA enrichment
  23. 2026-09-07 21:37 UTCEG score recompute
  24. 2026-09-07 21:37 UTCGHSA enrichment
  25. 2026-09-07 16:01 UTCEPSS rescore
  26. 2026-09-07 09:57 UTCGHSA enrichment
  27. 2026-09-06 22:10 UTCEG score recompute
  28. 2026-09-06 22:10 UTCGHSA enrichment
  29. 2026-09-06 13:47 UTCEPSS rescore
  30. 2026-09-06 10:28 UTCGHSA enrichment
  31. 2026-09-05 22:47 UTCEG score recompute
  32. 2026-09-05 22:47 UTCGHSA enrichment
  33. 2026-09-05 11:07 UTCGHSA enrichment
  34. 2026-09-04 23:27 UTCEG score recompute
  35. 2026-09-04 23:27 UTCGHSA enrichment
  36. 2026-09-04 11:26 UTCEG score recompute
  37. 2026-09-04 11:26 UTCGHSA enrichment
  38. 2026-09-04 05:07 UTCEPSS rescore
  39. 2026-09-03 23:44 UTCGHSA enrichment
  40. 2026-09-03 12:01 UTCGHSA enrichment
  41. 2026-09-03 00:16 UTCEG score recompute
  42. 2026-09-03 00:15 UTCGHSA enrichment
  43. 2026-09-02 14:12 UTCEPSS rescore
  44. 2026-09-02 12:32 UTCGHSA enrichment
  45. 2026-09-02 08:50 UTCGHSA enrichment
  46. 2026-09-01 21:08 UTCEG score recompute
  47. 2026-09-01 21:08 UTCGHSA enrichment
  48. 2026-09-01 17:22 UTCEG score recompute
  49. 2026-09-01 17:04 UTCEG score recompute
  50. 2026-09-01 16:25 UTCEG score recompute
  51. 2026-09-01 16:09 UTCEG score recompute
  52. 2026-09-01 16:08 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61753?
CVE-2026-61753 is a high vulnerability published on September 1, 2026. NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.
When was CVE-2026-61753 disclosed?
CVE-2026-61753 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61753 actively exploited?
CVE-2026-61753 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 69.3% of all scored CVEs.
What is the CVSS score of CVE-2026-61753?
CVE-2026-61753 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-61753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61753, 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-61753

Explore →

Is Your Infrastructure Affected by CVE-2026-61753?

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

Start Free Scan →Browse All CVEs