Information Disclosure in Lfprojects (CVE-2025-15381)
Summary
Vulnerability in Lfprojects (CVE-2025-15381). Data can be tampered with by attackers. Exploitable via NO_PERMISSIONS.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-15381 has been found in Lfprojects.
Attackers can target a specific entry point like NO_PERMISSIONS over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Lfprojects CVE-2025-15381" on the vendor's site.
CVE-2025-15381 (Lfprojects) — CWE-200 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: NO_PERMISSIONS
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Lfprojects. Attackers reach the vulnerable code path via NO_PERMISSIONS.
Check the vendor advisory for the affected versions of Lfprojects. Attack surface: NO_PERMISSIONS.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Lfprojects' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Lfprojects' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Lfprojectsを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security@huntr.dev
- web access.redhat.com
- web bugzilla.redhat.com
- web security.access.redhat.com