flairNLP Flair up to 0.15.1 Clustering clustering.py ClusteringModel.load deserialization

Summaryinfo

A vulnerability, which was classified as problematic, has been found in flairNLP Flair up to 0.15.1. This vulnerability affects the function ClusteringModel.load of the file flair/models/clustering.py of the component Clustering. The manipulation leads to deserialization. This vulnerability is documented as CVE-2026-76843. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in flairNLP Flair up to 0.15.1. This issue affects the function ClusteringModel.load of the file flair/models/clustering.py of the component Clustering. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The official Flair wheels for 0.15.0 and 0.15.1 still contain flair/models/clustering.py, whose ClusteringModel.load static method returns pickle.loads(joblib.load(str(model_file))) and so executes arbitrary Python while loading a model file. Loading a model supplied by an attacker therefore runs that attacker's code with the privileges of the loading process. This is the same sink and the same file as CVE-2024-10073, which records 0.15.0 as the fixed version on the basis that clustering support was dropped in that release; the module was removed from the documented API but remains present in the distributed artifact and reachable by importing flair.models.clustering directly, so the earlier record's fixed version does not hold for the shipped package.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-76843 since 08/19/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• flairNLP

Name

• Flair

Version

• 0.15.0
• 0.15.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion