Loading vulnerability…
Information currently not available to provide a detailed vulnerability description at the function/method level. Based on the provided content, CVE-2025-33213 is an unsafe deserialization (CWE-502) issue in the Trainer component of NVIDIA Merlin Transformers4Rec for Linux, where processing attacker-influenced serialized data can trigger a deserialization flaw. Successful exploitation may enable arbitrary code execution and can also result in denial of service, information disclosure, and data tampering.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in NVIDIA Merlin Transformers4Rec for Linux. No further details provided in the content.
A high-severity insecure deserialization vulnerability in NVIDIA Merlin's NVTabular Workflow component, allowing remote code execution and data exfiltration.
A high-severity deserialization vulnerability in the Trainer component of NVIDIA Merlin Transformers4Rec for Linux, allowing attackers to execute arbitrary code, trigger denial-of-service, disclose sensitive information, and tamper with data.
A deserialization vulnerability in the Trainer component of NVIDIA Merlin Transformers4Rec for Linux that can allow remote code execution, denial of service, information disclosure, and data tampering if exploited.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.