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があなたのプロジェクトに影響するか確認
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...