NVIDIA Tranformers4Rec contains a vulnerability where an attacker could cause improper deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.
CVE-2026-24232
Score 4.3 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026product-security/2026/5869 at main · NVIDIA/product-security · GitHub
https://github.com/NVIDIA/product-security/tree/main/2026/5869Vendor Advisories for CVE-2026-24232(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 16× in last 7d / 16× 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.
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 10:30 UTCEG score recompute
- 2026-07-26 10:30 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:07 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 20:08 UTCEG score recompute
- 2026-07-21 20:08 UTCGHSA enrichment
- 2026-07-21 17:20 UTCEG score recompute
- 2026-07-21 16:29 UTCEG score recompute
- 2026-07-21 16:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS p95CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-24232?
When was CVE-2026-24232 disclosed?
Is CVE-2026-24232 actively exploited?
What is the CVSS score of CVE-2026-24232?
How do I remediate CVE-2026-24232?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-24232
Is Your Infrastructure Affected by CVE-2026-24232?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.