CVE-2025-14922
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 · uneditedHugging Face Diffusers CogView4 Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Hugging Face Diffusers. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of checkpoints. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27424.
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 confidenceHugging Face Diffusers CogView4 checkpoint parsing lacks proper validation of user-supplied data during deserialization. This allows attackers to craft malicious checkpoint files that execute arbitrary code when loaded by victims, exploiting the deserialization process without additional software vulnerabilities.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed diffusers versionRun `pip show diffusers` or `python -c "import diffusers; print(diffusers.__version__)"`Affected if Version is unpatched and lacks safe deserialization for CogView4 checkpoints
-
Locate CogView4 checkpoint filesSearch for model files named 'cogview4' or checkpoint files with 'cogview4' in the path: `find . -iname '*cogview4*'`Affected if CogView4 checkpoint files exist in the environment and could be loaded
-
Verify checkpoint loading codeSearch codebase for `from_pretrained` or `load_checkpoint` calls referencing CogView4 models: `grep -r 'cogview4' . --include='*.py'`Affected if Code loads CogView4 checkpoints without additional validation
-
Check for unsafe pickle/deserialize operationsInspect diffusers source for checkpoint loading logic involving pickle or unsafe deserialization: examine the checkpoint loading pipeline in diffusers libraryAffected if Checkpoint loading uses pickle or unsafe deserialization without validation
-
Assess trust model for loaded checkpointsReview where and how checkpoints are loaded (local files, untrusted sources, user-uploaded): audit data flow into `from_pretrained` or similar functionsAffected if Checkpoints are loaded from untrusted or unverified sources
Environment is affected if running an unpatched diffusers version that loads CogView4 checkpoints, particularly from untrusted or unverified sources, due to unsafe deserialization in the checkpoint parsing process.
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 dataDo not load CogView4 checkpoints from untrusted or unverified sources. Await official patch from Hugging Face that implements safe deserialization for checkpoint loading.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14922 — 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-14922 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