Arbitrary code execution via unsafe model deserialization
Published Aug 24, 2026 · Updated Aug 28, 2026
Deserialization in Flair 0.15.0 through 0.15.1 allows attackers to execute arbitrary code by supplying a malicious model file. ClusteringModel.load in flair/models/clustering.py passes joblib-loaded model data to pickle.loads, which reconstructs attacker-controlled Python objects. Exploitation requires the loading process to open an attacker-supplied model, after which code runs with that process's privileges.
Summary
What happened
Deserialization in Flair 0.15.0 through 0.15.1 allows attackers to execute arbitrary code by supplying a malicious model file. ClusteringModel.load in flair/models/clustering.py passes joblib-loaded model data to pickle.loads, which reconstructs attacker-controlled Python objects. Exploitation requires the loading process to open an attacker-supplied model, after which code runs with that process's privileges.
The record
- CVE
- CVE-2026-76843
- Published
- Aug 24, 2026
- Updated
- Aug 28, 2026
- Vendor
- flairNLP
- Product
- Flair
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record 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=0.15.0 <=0.15.1
What conditions does exploitation require?
What is affected?
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