Service interruption via Donut regex backtracking
Published Jul 11, 2025 · Updated Jul 11, 2025
ReDoS in Hugging Face Transformers 4.51.3 and earlier allows remote attackers to interrupt Donut document processing with crafted tokens. DonutProcessor.token2json searches untrusted token text with the <s_(.*?)> pattern, whose lazy wildcard repeatedly backtracks when a closing delimiter is absent or delayed. Applications must pass attacker-controlled Donut token output to this method; excessive CPU use can hang document processing or its hosting service.
Summary
What happened
ReDoS in Hugging Face Transformers 4.51.3 and earlier allows remote attackers to interrupt Donut document processing with crafted tokens. DonutProcessor.token2json searches untrusted token text with the <s_(.*?)> pattern, whose lazy wildcard repeatedly backtracks when a closing delimiter is absent or delayed. Applications must pass attacker-controlled Donut token output to this method; excessive CPU use can hang document processing or its hosting service.
The record
- CVE
- CVE-2025-3933
- Published
- Jul 11, 2025
- Updated
- Jul 11, 2025
- Vendor
- Hugging Face
- Product
- Hugging Face Transformers
- Classifications
- CWE-1333, CAPEC-492, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2025CVE publishedPublication date reported by the CVE source.
- Jul 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <4.52.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo