CVE-2025-33213
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVIDIA Merlin Transformers4Rec for Linux contains a vulnerability in the Trainer component, where a user could cause a deserialization issue. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNVIDIA Merlin Transformers4Rec Trainer component contains a deserialization vulnerability where malicious or crafted serialized data processed by the Trainer could trigger unsafe deserialization, potentially leading to arbitrary code execution, denial of service, information disclosure, or data tampering.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Transformers4Rec is installedRun 'pip show transformers4rec' or check for the package in your Python environmentAffected if The package is not installed or cannot be found, the system is not affected by this specific vulnerability
-
Check the installed versionRun 'pip show transformers4rec' and note the Version field, then compare against NVIDIA's published affected version list for CVE-2025-33213Affected if The installed version falls within the affected version range published by NVIDIA for this CVE
-
Confirm Trainer component is in useSearch your codebase for imports like 'from transformers4rec import trainer' or 'Trainer' usage, and check if training pipelines use the Transformers4Rec Trainer classAffected if The Trainer component from Transformers4Rec is actively used in your environment
-
Inspect deserialization settingsExamine configuration files and code for pickle, joblib, or similar deserialization operations within Trainer workflows; look for model loading or data pipeline configurations that process serialized objectsAffected if The Trainer is configured to load or deserialize pickled/serialized data from untrusted sources or without validation
-
Check input validation in data pipelinesReview data preprocessing scripts that feed into Trainer for any validation applied to serialized input data before deserializationAffected if No input validation is performed on serialized data before it is processed by the Trainer
A system is likely affected if NVIDIA Merlin Transformers4Rec with a vulnerable version is installed and the Trainer component processes serialized data without input validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided patches when available; until then, restrict access to the Trainer component, validate all input data before deserialization, and network-segment systems running Transformers4Rec.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33213 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data