{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/cpes/cpe2.3ainformatik.hu-berlinflair0.14.0/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":[],"_cs_cpes":["cpe:2.3:a:informatik.hu-berlin:flair:0.14.0:*:*:*:*:*:*:*"],"_cs_cves":[{"cvss":7.8,"id":"CVE-2026-76843"},{"cvss":5,"id":"CVE-2024-10073"}],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["Flair (0.15.0)","Flair (0.15.1)"],"_cs_severities":["high"],"_cs_tags":[],"_cs_type":"advisory","_cs_vendors":["Flair"],"content_html":"\u003cp\u003eFlair versions 0.15.0 and 0.15.1 contain a critical deserialization vulnerability (CVE-2026-76843) stemming from the inclusion of the 'flair/models/clustering.py' module in distributed Python wheels. The 'ClusteringModel.load' static method improperly utilizes 'pickle.loads(joblib.load(...))' to process model files. This behavior allows an attacker to achieve arbitrary code execution by supplying a maliciously crafted model file to an application utilizing the library. This issue persists despite earlier efforts to address similar risks in CVE-2024-10073 by removing the module from the documented API; however, the code remains present in the distribution and reachable via direct import. Defenders should treat any application utilizing Flair 0.15.0 or 0.15.1 as potentially vulnerable to remote code execution if it processes user-supplied model files.\u003c/p\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation results in arbitrary code execution with the privileges of the application process. This vulnerability affects downstream systems and services that rely on the Flair library for machine learning model processing, potentially leading to full system compromise if the service runs with elevated permissions or lacks sandbox isolation.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eImmediately audit environments for the presence of Flair versions 0.15.0 and 0.15.1.\u003c/li\u003e\n\u003cli\u003eImplement strict input validation and access controls for any model files ingested by applications, as native serialization formats like pickle are inherently unsafe for untrusted data.\u003c/li\u003e\n\u003cli\u003eUpgrade to a version of Flair where the 'flair.models.clustering' module is entirely removed from the distributed artifact.\u003c/li\u003e\n\u003cli\u003eFor legacy systems that cannot be updated, implement process-level sandboxing (such as containers with minimal privileges) to isolate the execution of model loading routines.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-08-24T16:02:26Z","date_published":"2026-08-24T16:02:26Z","id":"https://feed.craftedsignal.io/briefs/2026-08-flair-deserialization/","summary":"Flair versions 0.15.0 and 0.15.1 contain a persistent deserialization vulnerability in the clustering module, enabling arbitrary code execution when processing untrusted model files.","title":"Remote Code Execution via Insecure Deserialization in Flair","url":"https://feed.craftedsignal.io/briefs/2026-08-flair-deserialization/"}],"language":"en","title":"CraftedSignal Threat Feed - Cpe:2.3:a:informatik.hu-Berlin:flair:0.14.0:*:*:*:*:*:*:*","version":"https://jsonfeed.org/version/1.1"}