CVE-2026-4035
Description
A flaw was found in MLflow. This vulnerability allows an attacker to exfiltrate sensitive server-side environment credentials. It occurs because the AI Gateway secrets can resolve environment variables, which are then sent to an attacker-controlled endpoint. This could lead to unauthorized access to cloud resources and potentially enable cross-boundary code execution.
Statement
This is a flaw in MLflow Server’s AI Gateway: if a gateway secret’s api_key uses a $ENV_VAR form, the server resolves it from pod environment variables and can send those values to a configured upstream api_base. The primary impact is credential disclosure (CWE-201), not direct remote code execution on the platform.
For OpenShift AI, most affected Konflux images embed the mlflow package (notebooks, pipelines, training runtimes) but do not run MLflow Server + AI Gateway in their default role. The clearest product exposure is odh-mlflow-rhel9, where the server component is actually shipped and operated. Exploitation requires Gateway configuration reachability and, in typical deployments, authenticated access (PR:L); unauthenticated abuse applies only where MLflow is deployed without basic-auth. Downstream artifact abuse depends on secondary use of leaked credentials, not a standalone RCE primitive in OpenShift AI itself. Hence, the impact is set to Important.
Mitigation
To mitigate this issue, restrict network access to the MLflow server to trusted clients only. Additionally, ensure that authentication mechanisms, such as basic-auth, are properly configured and enabled for MLflow deployments to prevent unauthenticated or low-privileged access to the AI Gateway. Consult MLflow documentation for specific configuration steps related to network access control and authentication. A restart or reload of the MLflow service may be required for changes to take effect.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.7 | 7.7 | 7.7 |
| Attack Vector | Network | Network | Network |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Changed | Changed | Changed |
| Confidentiality | High | High | High |
| Integrity Impact | None | None | None |
| Availability Impact | None | None | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Files or Directories; Read Memory; Read Application Data
Sensitive data may be exposed to attackers.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
