# CVE-2023-35625: Azure Machine Learning Compute Instance for SDK Users Information Disclosure Vulnerability

> Attackers can access sensitive information from Azure Machine Learning Compute Instances, potentially exposing user data.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2023
- **Updated:** 1 Jan 2025
- **Also known as:** GHSA-m5pc-86x8-wcxg, PYSEC-2026-1664

## What is CVE-2023-35625?

CVE-2023-35625 is a medium-severity vulnerability in Microsoft Azure Machine Learning, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Azure Machine Learning Compute Instance for SDK Users Information Disclosure Vulnerability

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-35625?

3 open source packages ship an affected version, including mltable. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mltable` | PyPI | All versions | 1.5.0 |
| `mltable` | PyPI | All versions | 1.5.0 |
| `mltable` | PyPI | All versions | 1.5.0 |

Products: Microsoft Azure Machine Learning Software Development Kit.

## How do I fix CVE-2023-35625?

Upgrade mltable to 1.5.0 or later.

## Is CVE-2023-35625 being exploited?

There is no known exploitation of CVE-2023-35625 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35625 and fix it if it is affected.

What it is: CVE-2023-35625 is a medium-severity vulnerability in Microsoft Azure Machine Learning, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35625 in the wild and no public exploit code.

Affected packages and fixed versions:
- mltable (PyPI): affected all versions; fixed in 1.5.0
- mltable (PyPI): affected all versions; fixed in 1.5.0
- mltable (PyPI): affected all versions; fixed in 1.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-35625/ (Markdown: https://insights.sbomify.com/CVE-2023-35625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-35625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-35625
- OSV: https://osv.dev/vulnerability/CVE-2023-35625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-35625/
Summaries are generated and may contain mistakes; the official description above is the record.