CVE-2026-2614: Arbitrary File Access in MLflow
प्लेटफ़ॉर्म
python
घटक
mlflow
में ठीक किया गया
3.10.0
CVE-2026-2614 describes an Arbitrary File Access vulnerability discovered in the mlflow/mlflow project. This flaw allows an unauthenticated attacker to read arbitrary files from the server's filesystem. The vulnerability impacts versions 3.9.0 and earlier of MLflow and is resolved in version 3.10.0.
इस CVE को अपने प्रोजेक्ट में पहचानें
अपनी requirements.txt फ़ाइल अपलोड करें और तुरंत जानें कि आप प्रभावित हैं या नहीं।
प्रभाव और हमले की स्थितियाँअनुवाद हो रहा है…
An attacker exploiting this vulnerability can gain unauthorized access to sensitive files stored on the MLflow server. This could include configuration files, credentials, or even source code. The ability to read arbitrary files represents a significant data breach risk. While the vulnerability requires an unauthenticated attacker, the ease of exploitation makes it a high-priority concern. Successful exploitation could lead to the exposure of proprietary algorithms, training data, or other confidential information crucial to machine learning workflows. This vulnerability shares similarities with other file access bypasses where insufficient validation of user-supplied paths leads to unintended file disclosure.
शोषण संदर्भअनुवाद हो रहा है…
CVE-2026-2614 was published on 2026-05-11. Its severity is rated HIGH with a CVSS score of 7.5. There is currently no indication of this vulnerability being actively exploited in the wild. No public Proof-of-Concept (PoC) exploits have been published. The vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog or has an EPSS score, suggesting a low to medium probability of exploitation.
खतरा खुफिया
एक्सप्लॉइट स्थिति
EPSS
0.04% (12% शतमक)
CVSS वेक्टर
इन मेट्रिक्स का क्या मतलब है?
- Attack Vector
- नेटवर्क — इंटरनेट के माध्यम से दूरस्थ रूप से शोषण योग्य। कोई भौतिक या स्थानीय पहुंच आवश्यक नहीं।
- Attack Complexity
- निम्न — कोई विशेष शर्त नहीं। विश्वसनीय रूप से शोषण योग्य।
- Privileges Required
- कोई नहीं — बिना प्रमाणीकरण के शोषण योग्य।
- User Interaction
- कोई नहीं — स्वचालित और मूक हमला। पीड़ित कुछ नहीं करता।
- Scope
- अपरिवर्तित — प्रभाव केवल कमज़ोर घटक तक सीमित।
- Confidentiality
- उच्च — पूर्ण गोपनीयता हानि। हमलावर सभी डेटा पढ़ सकता है।
- Integrity
- कोई नहीं — अखंडता पर कोई प्रभाव नहीं।
- Availability
- कोई नहीं — उपलब्धता पर कोई प्रभाव नहीं।
प्रभावित सॉफ्टवेयर
कमजोरी वर्गीकरण (CWE)
समयरेखा
- प्रकाशित
- संशोधित
- EPSS अद्यतन
शमन और वर्कअराउंडअनुवाद हो रहा है…
The primary mitigation for CVE-2026-2614 is to upgrade MLflow to version 3.10.0 or later, which contains the fix. If upgrading immediately is not feasible, consider implementing a temporary workaround by restricting access to the createmodelversion() handler. This can be achieved through network segmentation or access control lists (ACLs) to limit access to authorized users only. Additionally, monitor MLflow server logs for any suspicious activity related to file access requests, particularly those involving the mlflow.prompt.isprompt tag. After upgrading, confirm the fix by attempting to create a model version with a malicious mlflow.prompt.is_prompt tag and verifying that the server denies the request and does not serve arbitrary files.
कैसे ठीक करेंअनुवाद हो रहा है…
Actualice a la versión 3.10.0 o posterior para mitigar la vulnerabilidad. Esta versión corrige el problema de validación de la fuente al leer archivos, evitando la lectura arbitraria de archivos del sistema.
अक्सर पूछे जाने वाले सवालअनुवाद हो रहा है…
What is CVE-2026-2614 — Arbitrary File Access in MLflow?
CVE-2026-2614 is a HIGH severity vulnerability in MLflow versions 0.0.0–3.10.0 that allows an unauthenticated attacker to read arbitrary files from the server's filesystem by exploiting a flaw in the createmodel_version() handler.
Am I affected by CVE-2026-2614 in MLflow?
You are affected if you are using MLflow versions 3.9.0 or earlier. Upgrade to version 3.10.0 to resolve the vulnerability.
How do I fix CVE-2026-2614 in MLflow?
Upgrade MLflow to version 3.10.0 or later. As a temporary workaround, restrict access to the createmodel_version() handler.
Is CVE-2026-2614 being actively exploited?
There is currently no indication that CVE-2026-2614 is being actively exploited in the wild, and no public PoCs are available.
Where can I find the official MLflow advisory for CVE-2026-2614?
Refer to the MLflow project's security advisories and release notes for the official advisory regarding CVE-2026-2614: [https://mlflow.org/docs/latest/security.html](https://mlflow.org/docs/latest/security.html)
क्या आपका प्रोजेक्ट प्रभावित है?
अपनी डिपेंडेंसी फ़ाइल अपलोड करें और तुरंत जानें कि यह CVE और अन्य आपको प्रभावित करती हैं या नहीं।
इस CVE को अपने प्रोजेक्ट में पहचानें
अपनी requirements.txt फ़ाइल अपलोड करें और तुरंत जानें कि आप प्रभावित हैं या नहीं।
अपने Python प्रोजेक्ट को अभी स्कैन करें — कोई खाता नहीं
Upload your requirements.txt and get the vulnerability report instantly. No account. Uploading the file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
अपनी डिपेंडेंसी फ़ाइल ड्रैग और ड्रॉप करें
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...