Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2025-15381

HIGH

CVE-2025-15381 is a high-severity (CVSS 7.1) Information Exposure vulnerability in lfprojects mlflow. O3 Security detects and blocks CVE-2025-15381 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

In the latest version of mlflow/mlflow, when the `basic-auth` app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated…

Published
Mar 27, 2026
Updated
Jul 15, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

Description

In the latest version of mlflow/mlflow, when the basic-auth app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with NO_PERMISSIONS on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by allowing unauthorized creation of assessments. Deployments using mlflow server --app-name=basic-auth are affected.

Affected Products

1 product · 1 configurations
Application
mlflowlfprojects
all

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every lfprojects mlflow deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Remediation status

    No patch has shipped for CVE-2025-15381 yet — track the lfprojects mlflow advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2025-15381 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2025-15381. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In the latest version of mlflow/mlflow, when the `basic-auth` app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with `NO_PERMISSIONS` on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by allowing unauthorized creation of assessments. Deployments using `mlflow server --app-name=basic-auth` are affected.
O3 Security · Runtime Protection

Is CVE-2025-15381 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2025-15381 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.