Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious checkpoint at attacker-controlled URL
-
DeliveryVictim calls load_pretrained_params() on it
-
Exploittorch.load unpickles crafted payload
-
ExecutionExecute arbitrary Python code
-
ImpactCompromise host under loader's privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that (1) the victim application calls docTR's load_pretrained_params() on a checkpoint whose path or URL is attacker-controlled or attacker-tamperable, and (2) the environment runs a PyTorch release before 2.6, since torch 2.6+ defaults torch.load to weights_only=True and blocks arbitrary pickle execution. Key limiting factors: it is not self-triggering - a user/process must actively load the malicious checkpoint (UI:P), and deployments already on torch ≥2.6 or on patched docTR (post-commit 687503d) are not exploitable even against untrusted checkpoints. No authentication bypass is involved; the attacker's leverage is supplying the poisoned model artifact. |
| Impact | This is a genuine but conditionally-gated code-execution flaw rather than a drop-everything emergency. The CWE-502 pickle deserialization pattern (torch.load without weights_only=True) is a well-understood, reliable RCE primitive, and the fix is confirmed by the vendor commit (687503d) adding weights_only=True. However, multiple signals temper the real-world risk: the vendor-provided CVSS 4.0 vector carries AT:P (a specific attack requirement) and UI:P (passive user interaction), meaning exploitation depends on the victim loading an attacker-controlled checkpoint AND on running torch before 2.6 - torch 2.6+ already defaults to weights_only=True, which neutralizes the bug regardless of docTR version. No KEV listing and no EPSS score are present in the input, and no public exploit or POC is referenced (only the VulnCheck advisory and the upstream issue/patch), so there is no evidence of active exploitation or weaponization. The AV:N label reflects that the malicious checkpoint can be URL-supplied, but this is not a classic unauthenticated remote-service exploit - the attacker must get a victim to point docTR at a poisoned checkpoint. Net: a legitimately high-severity, patch-now issue for anyone loading untrusted models on older torch, but not a wormable internet-facing threat. |
| Exploit ScenarioDerived | An attacker publishes or links a malicious docTR model checkpoint (e.g. on a model hub, via a tampered download URL, or a shared file) containing a crafted pickle payload. A victim running docTR ≤1.1.0 on torch <2.6 calls load_pretrained_params() against that checkpoint, and torch.load deserializes the pickle, executing the attacker's Python code with the privileges of the loading process. No public POC is referenced, but the technique is standard and trivially reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Arbitrary Python code execution in docTR through 1.1.0 is possible when load_pretrained_params() deserializes an attacker-controlled or tamperable checkpoint on PyTorch releases before 2.6. Unauthenticated attackers can supply the poisoned model artifact, but exploitation is conditionally gated: the victim application must load that checkpoint from a path or URL the attacker controls, and PyTorch must predate 2.6, where torch.load began defaulting to weights_only=True. No public exploit code or CISA KEV entry was identified at time of analysis, and this is a genuine but conditionally-gated code-execution flaw rather than a drop-everything emergency.
RemediationAI
Apply the vendor fix commit 687503dd15592483c4699ee51280b41938579a9e or upgrade to a docTR release that includes it; the exact released patched version is not specified in the provided data, so upstream fix availability is confirmed via commit/PR while a tagged release is not independently confirmed. The commit changes torch.load(..., weights_only=True), so patched docTR blocks pickle-based payload execution even against a malicious checkpoint. Also upgrade PyTorch to 2.6 or later, where weights_only=True is the default, or explicitly pass weights_only=True on any remaining torch.load calls; note that weights_only=True can reject checkpoints containing non-tensor Python objects, so re-save models as plain state_dicts or safetensors if compatibility breaks. Where patching is not immediately possible, avoid loading checkpoints from untrusted or user-supplied paths and URLs, verify checkpoint checksums/signatures, and restrict outbound network access to approved model sources; these controls reduce exposure but do not fully remove the deserialization risk if an attacker can still influence the checkpoint. Advisory: https://www.vulncheck.com/advisories/doctr-through-1.1.0-unsafe-deserialization-rce-via-load-pretrained-params and issue https://github.com/mindee/doctr/issues/2175.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is CWE-502 unsafe deserialization in docTR's model-loading utility, load_pretrained_params() in doctr/models/utils/pytorch.py. That function calls torch.load(archive_path, map_location='cpu') without weights_only=True, so on PyTorch releases before 2.6 the checkpoint is unpickled with full pickle semantics; a malicious checkpoint can embed pickle opcodes that invoke arbitrary Python callables when loaded, executing with the privileges of the docTR process. The CPE cpe:2.3:a:mindee:doctr:*:*:*:*:*:*:*:* identifies Mindee docTR as the affected product, and the vendor fix commit 687503dd15592483c4699ee51280b41938579a9e adds weights_only=True to that torch.load call. The vulnerability is not self-triggering: it requires the application to load a checkpoint whose path or URL is attacker-controlled or attacker-tamperable, and it is neutralized on PyTorch 2.6+ or on docTR builds containing the fix.
Know when Doctr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
AV:N since checkpoints can be URL-supplied, UI:R because the victim must load the malicious checkpoint, AC:H as exploitation is gated on torch <2.6; full C/I/A impact from arbitrary code execution.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
docTR through 1.1.0 contains an unsafe deserialization vulnerability in load_pretrained_params() that loads checkpoints with torch.load without weights_only=True. Attackers who control a local or URL-supplied checkpoint can embed a malicious pickle payload to execute Python code with the loading process's privileges on torch releases before 2.6.
Executive ViewAI
docTR through 1.1.0 can execute arbitrary Python code when it deserializes a tampered model checkpoint on PyTorch releases before 2.6, affecting any team that runs OCR or document-processing pipelines built on this stack. Exposure is concentrated in environments that fetch pretrained models from external URLs or user-writable paths, since the attacker must first get the victim application to load their checkpoint; locked-down deployments that only load internally vetted artifacts face materially lower risk. Leadership should track this as a scheduled remediation item rather than an emergency: no public exploit code or CISA KEV entry was identified at time of analysis, and a vendor patch is available.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
EUVD-2026-104396
GHSA-rh68-f334-2256
NVD
CVE.org
EPSS
VulDB
Exploit-DB