{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:71f244ac-8c70-533e-b08c-4d4f531e73f9", "version": 1, "metadata": { "supplier": { "name": "TuxCare", "url": [ "https://tuxcare.com" ] } }, "components": [ { "name": "mlflow", "purl": "pkg:pypi/mlflow@2.22.4.post11+tuxcare", "type": "library", "bom-ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare", "version": "2.22.4.post11+tuxcare", "pedigree": { "ancestors": [ { "name": "mlflow", "purl": "pkg:pypi/mlflow@2.22.4", "type": "library", "version": "2.22.4" } ] }, "supplier": { "url": [ "https://tuxcare.com" ], "name": "TuxCare" } } ], "vulnerabilities": [ { "id": "CVE-2023-6709", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:a62ab01e-1e8a-58d1-bc97-7729798ad348", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6709 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6753", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7e45da52-963c-54f7-871b-339d423c520d", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6753 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6831", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:18c72a0d-b51b-5257-9577-6ed646b546f5", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6831 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6909", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:aa1277cc-eef4-58ab-a520-51e052a74285", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6909 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6940", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:73514c91-e66f-5574-96a1-d25eb829a850", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6940 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6974", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7d8f4f05-bb64-5181-b11e-9fb917c135c7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6974 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6975", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:8783c006-79d0-583a-8c97-0cdbf786b49e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6975 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6976", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:285556b5-f18a-5dba-b7c4-b71a4b0bb7d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6976 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2023-6977", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:29c40bd3-f374-5ca8-89c3-7725d5a98a26", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2023-6977 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-1483", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:14ea89ca-f684-5009-87f0-b352323de01c", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-1483 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-1558", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:453f2f00-20b8-515d-880e-3442b05eb813", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-1558 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-1560", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:2b7d1c2a-61b8-51c5-8342-440c33056204", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-1560 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-1593", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:04365eed-2fa0-5097-bf7f-7c5ff36d44e8", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-1593 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-1594", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:b072e572-deff-5c80-89c4-caf659a2505e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-1594 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-27132", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:585a6dc6-99eb-5a4c-bf62-29881fb0b3e4", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27132 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-27133", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:d7732353-e122-5b3d-b11c-2164f3656424", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27133 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-27134", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7e5ec2dc-146d-517e-9b84-39f84614c0b7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-27134 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-2928", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:2138a677-a19c-5abd-a46b-39cb332ad881", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-2928 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-3099", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:36c31e3b-f46a-569f-b1d9-731d07b806bd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-3099 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 CVE-2024-3099 (URL-encoded model names vulnerability) is NOT present in mlflow 2.22.4 at HEAD (7af4770cd). The upstream fix (commit a924d129e \"Disallow % in model names\", authored by daniel.lok@databricks.com on 2024-03-21) was already included in the upstream release that TuxCare onboarded. The defense code validates model names and rejects any containing '%' character, preventing URL-encoded ...", "justification": "code_not_present" } }, { "id": "CVE-2024-3573", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:81049804-c247-5bcc-a42c-14856b696556", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-3573 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37052", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:1675c61a-50ee-5e8d-a045-96a9ec57033e", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37052 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37053", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:bb1288fa-fe1a-5b88-8530-274028d2cbfc", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37053 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37054", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:c6a06941-5967-5d89-8c2f-a754c1e537e0", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37054 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37055", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:38d08bb3-c497-5852-b921-45380116c4bf", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37055 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37056", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:c9d97c42-b36d-5284-874f-f08ed516ea54", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37056 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37057", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:bbbe306d-1f3b-58ae-88f9-248afc1f0e02", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37057 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37058", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:ff214d72-4e6e-595e-ab27-1373a48549d7", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37058 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37059", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7e02635d-5fa8-5e86-ad69-bb49a40971a6", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-37059 does not affect version 2.22.4.post11+tuxcare of mlflow. already_fixed \u2014 fix already present in target (commit c6c9002f29)" } }, { "id": "CVE-2024-37060", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:45aaf3e5-ae23-5f37-8dfd-9dabfda11102", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37060 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-37061", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:f8ec51ef-5859-5a9a-b522-f177788303e2", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-37061 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-4263", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:a7471e36-7229-51ac-83cc-1f95d6fb20d0", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2024-4263 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 CVE-2024-4263 is NOT present in mlflow 2.22.4. The vulnerability allowed users with EDIT permissions to delete artifacts by incorrectly checking `can_update` instead of `can_manage` for DELETE operations. The upstream fix (commit cfa71879a \"Fix #11308\" by harupy) was already included in the mlflow 2.22.4 release that TuxCare onboarded. The target code correctly implements the fix: function `val...", "justification": "code_not_present" } }, { "id": "CVE-2024-6838", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:8f8dfa3b-c0a7-57d4-a1f9-6add24cd5870", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-6838 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2024-8859", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:73f17a10-8884-5257-9f63-fa649f9138df", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2024-8859 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-0453", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:eab21e0a-785d-5a2f-a2e0-db1c69327325", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-0453 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-10279", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:4d33272d-8d30-59ef-9f51-8015005382a0", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-10279 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-11200", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:6a3bd803-2338-5ff5-8747-108f0ca4fd4f", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-11200 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-11201", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:008a9257-c541-5775-9f78-19f25cc29b36", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2025-11201 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-14279", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:660f9c55-7348-5bca-a7a8-3d40cafbb0a7", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14279 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-14287", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:df1f43da-d4dc-5bb6-91b1-0c36153bba92", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-14287 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-1474", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:ac78e93f-3d7d-5546-b118-05fe0382b5e3", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-1474 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 CVE-2025-1474 (passwordless user account creation) is NOT present in mlflow 2.22.4. The vulnerability was fixed in upstream commit 1f74f3f24 by WeichenXu@databricks.com, which shipped in v2.22.0rc0 (April 2025) - before the target version 2.22.4. The fix adds `_validate_password` validation in `create_user` method that rejects passwords that are None or shorter than 12 characters. This defense ...", "justification": "code_not_present" } }, { "id": "CVE-2025-15031", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:b65d5257-1c80-51ea-8c34-af8708d2133e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-15031 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-15036", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:67cb7e5f-d60d-55f1-9767-5b71781119b5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-15036 does not affect version 2.22.4.post11+tuxcare of mlflow. Version 2.22.4 is not vulnerable. Summary: The target repository (MLflow v2.22.4.post1+tuxcare) is NOT VULNERABLE to CVE-2025-15036. While the vulnerable code pattern (tarfile.extractall in extract_archive_to_dir) exists, the security fix has been backported from upstream v3.9.0. The check_tarfile_security function is properly implemented and called before tar extraction, preventing path traversal attacks. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2025-15379", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:29026c94-61d0-56e8-a805-f2843ad036f7", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-15379 does not affect version 2.22.4.post11+tuxcare of mlflow. Patches already applied: a22ce7157f646bdce4c95106fc38ccc9ca289205 (already in target via 3e7233561c 'PYELSCVE-466: Fix for AIKIDO-2025-11008')" } }, { "id": "CVE-2025-15381", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:de8a8bb5-f2fa-57d7-a16f-009600d00b93", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-15381 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2025-52967", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:f7d9b918-1e5b-55c0-8f59-7674a17f9558", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2025-52967 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 The target MLflow 2.22.4 repository is NOT affected by CVE-2025-52967. The vulnerability (lack of gateway_path validation in gateway_proxy_handler) has been fixed by an upstream commit that shipped in MLflow v2.22.1. The fix adds comprehensive format validation via _validate_gateway_path() function (lines 1377-1395) that restricts gateway_path to specific allowed patterns based on HTTP method, ...", "justification": "code_not_present" } }, { "id": "CVE-2026-0545", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:70faca94-5484-56c9-8bb6-a5b6485b33a4", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-0545 does not affect version 2.22.4.post11+tuxcare of mlflow. Version 2.22.4 is not vulnerable. Summary: The target repository (MLflow v2.22.4.post2+tuxcare) is NOT vulnerable to CVE-2026-0545. The vulnerable feature (FastAPI job execution endpoints under /ajax-api/3.0/jobs/*) was introduced in MLflow v3.5.0 (September 2025), which is significantly later than the target version v2.22.4. The target repository does not contain the vulnerable code, job execution infrastructure, or FastAPI authentication middleware. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2026-0596", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:a0de532e-c3ff-5ca0-8f72-d4c9a57aa547", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-0596 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-10803", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:337b50f9-3206-5b8a-80c5-03a7bfb47777", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-10803 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-116691", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:c32227cc-0971-50da-9ce8-214edaa9c936", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-116691 affects version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-2033", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:b2754e03-c9ec-5767-8d6b-82930f053ea8", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-2033 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-2393", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7447ac66-13db-59d2-85aa-6435004322bc", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-2393 does not affect version 2.22.4.post11+tuxcare of mlflow. Version 2.22.4 is not vulnerable. Summary: Target repository version 2.22.4 does not contain the vulnerable webhook feature. Webhooks were introduced in MLflow v3.3.0 (commit 3094ab608b, August 2025), which is significantly after the target version. The vulnerable code pattern described in CVE-2026-2393 never existed in this version of the codebase. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2026-2614", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:5ecce7f4-0958-594d-92b4-9af1539dd7b1", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-2614 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-2635", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:b705ec91-13f1-59e0-a862-9359ca408c60", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-2635 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-2651", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:d7ed932e-3021-5510-b4bb-58b02a14143e", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-2651 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-2652", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:bd55eeb0-836e-5bab-99e3-62855a945b0b", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-2652 does not affect version 2.22.4.post11+tuxcare of mlflow. Version 2.22.4 is not vulnerable. Summary: The target repository (mlflow version 2.22.4) is NOT vulnerable to CVE-2026-2652. The vulnerable FastAPI authentication middleware code was introduced in version 3.9.0, which is significantly newer than the target version. In version 2.22.4, all routes are handled by Flask via WSGI middleware, eliminating the architectural mismatch between Flask and FastAPI authentication that causes this vulnerability. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2026-2734", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:2a439b25-d577-5e83-9014-3a0ab76ff325", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-2734 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-3198", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:9096ab6f-afd9-5f70-8f7a-ca055edab5a5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-3198 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 MLflow version 2.22.4 is not affected by CVE-2026-3198. The vulnerability describes missing authorization handlers for Gateway API protobuf endpoints (ListGatewaySecretInfos, ListGatewayEndpoints, ListGatewayModelDefinitions) in the BEFORE_REQUEST_HANDLERS dictionary when using basic-auth. However, version 2.22.4 uses a fundamentally different Gateway architecture - a separate FastAPI-based ser...", "justification": "code_not_present" } }, { "id": "CVE-2026-33865", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:7a718286-3d6b-5816-accf-3dbcbf0e39b5", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-33865 does not affect version 2.22.4.post11+tuxcare of mlflow. Frontend-only vulnerability; the TuxCare build ships no web UI. CVE-2026-33865 lives entirely in the MLflow JavaScript frontend (yaml.load -> yaml.safeLoad in ShowArtifactLoggedModelView.tsx and useValidateLoggedModelSignature.ts). Verified on the shipped artifact mlflow-2.22.4.post9+tuxcare-py3-none-any.whl (release pipeline 104717): 670 files, zero entries under mlflow/server/js/, no js/build directory, 6.0 MB against 27.7 MB for the upstream PyPI wheel of the same version. mlflow/server/__init__.py sets static_folder=\"js/build\" and guards on index.html existing, so the REST API is served and the UI page is absent. The vulnerable code is not present in what customers install.", "justification": "code_not_present" } }, { "id": "CVE-2026-33866", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:ee86e7fa-472b-5e2b-a7ff-5875abbbedfd", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-33866 does not affect version 2.22.4.post11+tuxcare of mlflow. Version 2.22.4 is not vulnerable. Summary: The target MLflow repository (version 2.22.4) does not contain the vulnerable 'Logged Models' feature described in CVE-2026-33866. This feature was introduced in MLflow 3.x, significantly after this version. The vulnerable AJAX artifact download endpoint and associated functionality do not exist in the codebase. [terminalized not_affected from patch_application_manual/not_vulnerable]", "justification": "code_not_present" } }, { "id": "CVE-2026-4035", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:fce1feb8-ec64-5591-bef7-82cf0f728afd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4035 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-4137", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:f1054e04-895a-5ab4-9770-1dc2053e7478", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-4137 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "CVE-2026-53995", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:03d37a6a-c2d4-5b4d-bb17-c47cfe0bb475", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-53995 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 MLflow version 2.22.4 is not affected by CVE-2026-53995. While the codebase contains a potentially vulnerable mkdir() function that uses os.path.join without path traversal validation, user-supplied trace IDs never reach this dangerous operation. The start_trace endpoint generates trace IDs server-side via UUID (not user-controlled), and all endpoints that accept user-supplied trace IDs (end_tr...", "justification": "code_not_reachable" } }, { "id": "CVE-2026-64849", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:f8b79a81-fb21-56dd-8967-662fc4a7e32f", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-64849 does not affect version 2.22.4.post11+tuxcare of mlflow. not_affected \u2014 MLflow version 2.22.4 does not contain the webhooks feature that is vulnerable to CVE-2026-64849. The webhooks functionality (including the webhook URL validation, HTTP delivery mechanism, and the `/api/2.0/mlflow/webhooks/{id}/test` endpoint) was introduced in version 3.4.0, which is significantly later than the target version 2.22.4. Without the webhooks feature, the SSRF vulnerability descri...", "justification": "code_not_present" } }, { "id": "CVE-2026-8147", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:3832bdb4-5ffc-5d63-bc24-49979e91f2fd", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-8147 is fixed in version 2.22.4.post11+tuxcare of mlflow." } }, { "id": "GHSA-gqvg-gmmx-x4hm", "affects": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ], "bom-ref": "urn:uuid:43d3115e-3e8c-5a05-8b1e-9455167d1e7f", "analysis": { "state": "resolved", "detail": "Vulnerability GHSA-gqvg-gmmx-x4hm is fixed in version 2.22.4.post11+tuxcare of mlflow." } } ], "dependencies": [ { "ref": "pkg:pypi/mlflow@2.22.4.post11+tuxcare" } ] }