CVE-2025-33233
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 all platforms contains a vulnerability where an attacker could cause code injection. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, 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 contains a code injection vulnerability that allows an attacker to inject and execute arbitrary code. This vulnerability can be exploited to achieve code execution, privilege escalation, information disclosure, and data tampering within the affected application context.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify if Transformers4Rec is installedRun 'pip show transformers4rec' or check your Python environment for the transformers4rec packageAffected if The package is present in your environment
-
Determine installed versionRun 'pip show transformers4rec' and note the Version field, then compare against any published affected version ranges from NVIDIA's security advisoryAffected if Your installed version falls within the affected version range
-
Locate dynamic code execution usage in Transformers4RecSearch the transformers4rec installation directory for usage of eval(), exec(), compile(), or similar functions (e.g., grep -r 'eval\|exec\|compile' in the package directory)Affected if These functions are present and process user-controlled input without sanitization
-
Inspect input handling code pathsReview code that processes user inputs within Transformers4Rec, focusing on modules that accept external data (such as feature extraction, data loading, or configuration parsing)Affected if User-supplied data reaches dynamic execution functions without validation
-
Check configuration for unsanitized inputsExamine configuration files, model parameter inputs, or API endpoints within Transformers4Rec that accept user-provided valuesAffected if User-controllable parameters are passed to dynamic execution contexts
You are affected if you have Transformers4Rec installed with a vulnerable version AND your environment allows unsanitized user input to reach dynamic code execution functions within the application.
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 dataRemediate by implementing strict input validation and sanitization on all user-controlled inputs processed by Transformers4Rec, and audit code paths where dynamic execution occurs to ensure no unsanitized data reaches eval(), exec(), or similar functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33233 — 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-33233 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