CVE-2026-76843
RCE via pickle when loading attacker-crafted Flair model files.
Is CVE-2026-76843 being exploited?
Not confirmed. CVE-2026-76843 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-76843?
CVE-2026-76843 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76843?
Not known from our data. No patch reference has been recorded for CVE-2026-76843, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-76843 affect?
CVE-2026-76843 affects flair 0.15.0, flair 0.15.1, Python environments loading untrusted Flair models, ML inference servers, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76843?
Do not load untrusted Flair models; remove clustering.py from installs; restrict model sources and update when vendor issues a patch.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution as the loading process user by loading a malicious Flair model; can lead to data theft, lateral movement, and persistence.
Immediate action required
- affected>= 0.15.0 and <= 0.15.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.