CVE-2026-61773

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
16%
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-61773

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61773?
CVE-2026-61773 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-61773 disclosed?
CVE-2026-61773 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-61773 actively exploited?
CVE-2026-61773 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 84.1% of all scored CVEs.
What is the CVSS score of CVE-2026-61773?
CVE-2026-61773 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-61773?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61773, 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-61773

Explore →

Is Your Infrastructure Affected by CVE-2026-61773?

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

Start Free Scan →Browse All CVEs