dbcve.org
Transformers4recApplication · Nvidia

CVE-2026-24162

HIGH · 7.8 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 2026-03-11 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
NVIDIA Transformers4Rec for Linux 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.

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 · high confidence

NVIDIA Transformers4Rec for Linux contains an insecure deserialization vulnerability where the application deserializes untrusted data without proper validation. This improper handling of deserialized data can allow an attacker to manipulate the deserialization process to execute arbitrary code, tamper with data, or disclose sensitive information.

MitigationAvoid deserializing untrusted data wherever possible. If deserialization is required, use safe serialization formats (e.g., JSON, Protocol Buffers) instead of pickle or similar unsafe formats, implement strict input validation, and apply updates or patches released by NVIDIA.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Transformers4recApplication
Affected:< 2026-03-11

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Transformers4Rec is installed
    Run `pip list | grep -i transformers4rec` or `pip show transformers4rec` to see if the package is installed in your Python environment
    Affected if The package is not installed means you are not affected by this vulnerability in this product
  2. Determine installed version
    Run `pip show transformers4rec` and note the Version field, or check the package metadata via `python -c "import transformers4rec; print(transformers4rec.__version__)"`
    Affected if Version is lower than 2026-03-11 - compare your version number against this threshold
  3. Identify deserialization usage in your code
    Search your codebase for usage of pickle, joblib, or Transformers4Rec's SequenceSchema, Schema, or similar serialization methods: grep -r 'pickle.load\|joblib.load\|\.from_parquet\|Schema\.from\|' $(find . -name "*.py")
    Affected if Code deserializes untrusted data using pickle, joblib, or the library's schema/sequence serialization features - this is required for exploitation
  4. Check for untrusted input sources
    Review your data pipeline to determine if any serialized data from external or untrusted sources (user uploads, API inputs, network data) is being passed to Transformers4Rec deserialization functions
    Affected if Untrusted serialized data flows into Transformers4Rec's deserialization routines - this creates the attack surface
  5. Inspect library serialization dependencies
    Examine transformers4rec's installed dependencies: pip show transformers4rec | grep -i requires. Also check if the library uses unsafe serialization by default in its schema or sequence handling modules
    Affected if The library uses pickle-based serialization by default without input validation

You are affected if Transformers4Rec is installed with a version earlier than 2026-03-11 AND your application deserializes untrusted data using the library's serialization features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2026-03-11 or later
Fixed in 2026-03-11
Interim mitigation

Avoid deserializing untrusted data wherever possible. If deserialization is required, use safe serialization formats (e.g., JSON, Protocol Buffers) instead of pickle or similar unsafe formats, implement strict input validation, and apply updates or patches released by NVIDIA.

Recommended fix Moderate confidence

transformers4rec version 2026-03-11 or later

  1. 1. Identify the current installed version of transformers4rec by running: pip show transformers4rec or conda list transformers4rec
  2. 2. Upgrade transformers4rec to the fixed version by running: pip install transformers4rec==2026.03.11 (or pip install --upgrade transformers4rec to get the latest version which includes the fix)
  3. 3. Verify the upgrade was successful by running: pip show transformers4rec and confirming the version is 2026-03-11 or later
  4. 4. Test that your applications using transformers4rec function correctly after the upgrade
  5. 5. Review release notes for any breaking changes or migration considerations
Caveat Review NVIDIA release notes for version 2026-03-11 for any potential breaking changes or API modifications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Transformers4rec Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24162 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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