CVE-2025-33245

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic
https://www.cve.org/CVERecord?id=CVE-2025-33245

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
nemo-toolkit0.10.0 ... 2.6.0rc0 (102 versions)2.6.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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-20 20:15 UTCEPSS rescore
  2. 2026-09-19 14:33 UTCOSV refresh
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:29 UTCEPSS rescore
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-16 05:14 UTCEPSS rescore
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-10 09:33 UTCEPSS rescore
  12. 2026-09-08 21:59 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:38 UTCEPSS rescore
  19. 2026-08-31 18:04 UTCOSV refresh
  20. 2026-08-30 19:16 UTCEPSS rescore
  21. 2026-08-30 01:21 UTCEPSS rescore
  22. 2026-08-28 21:40 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-26 14:45 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
Show 32 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-17 13:46 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-14 09:51 UTCEG score recompute
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 02:10 UTCEG score recompute
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 07:32 UTCEG score recompute
  16. 2026-08-09 14:13 UTCEG score recompute
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-08 16:36 UTCEPSS rescore
  19. 2026-08-07 21:42 UTCEG score recompute
  20. 2026-08-07 16:26 UTCEPSS rescore
  21. 2026-08-06 13:46 UTCEPSS rescore
  22. 2026-08-06 03:36 UTCEG score recompute
  23. 2026-08-04 15:09 UTCEPSS rescore
  24. 2026-08-04 10:37 UTCEPSS rescore
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 20:23 UTCEG score recompute
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 04:15 UTCEPSS rescore
  29. 2026-07-30 16:27 UTCEPSS rescore
  30. 2026-07-30 01:29 UTCEPSS rescore
  31. 2026-07-28 15:35 UTCEPSS rescore
  32. 2026-07-27 13:29 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-33245?
CVE-2025-33245 is a high vulnerability published on February 18, 2026. NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.
When was CVE-2025-33245 disclosed?
CVE-2025-33245 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-33245 actively exploited?
CVE-2025-33245 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.7% of all scored CVEs.
What is the CVSS score of CVE-2025-33245?
CVE-2025-33245 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-33245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-33245, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-33245

Explore →

Is Your Infrastructure Affected by CVE-2025-33245?

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

Start Free Scan →Browse All CVEs