NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2023-35625 — mltable

MEDIUM

CVE-2023-35625 is a medium-severity (CVSS 4.7) Information Exposure vulnerability in mltable. A fix is available for mltable — see the affected versions and patch details below.

Exposure of Sensitive Information in mltable

Also known asPYSEC-2026-1664
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-35625.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.16%0.51%0.86%1.21%0.7%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍mltable

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Azure Machine Learning Compute Instance for SDK Users Information Disclosure Vulnerability

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImltableall versions1.5.0pip install --upgrade 'mltable==1.5.0'

Affected Products

1 product · 1 configurations
Application
azure machine learning software development kitmicrosoft
< 1.5.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mltable, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update mltable to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-35625 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Azure Machine Learning Compute Instance for SDK Users Information Disclosure Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2023-35625 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2023-35625: mltable Info Disclosure — Fixed in 1.5.0