CVE-2025-54413

CVE-2025-54413 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-351.

Key facts

Description

skops is a Python library which helps users share and ship their scikit-learn based models. Versions 0.11.0 and below contain an inconsistency in MethodNode, which can be exploited to access unexpected object fields through dot notation. This can be used to achieve arbitrary code execution at load time. While this issue may seem similar to GHSA-m7f4-hrc6-fwg3, it is actually more severe, as it relies on fewer assumptions about trusted types. This is fixed in version 12.0.0.

Frequently asked questions

What is CVE-2025-54413?
skops is a Python library which helps users share and ship their scikit-learn based models. Versions 0.11.0 and below contain an inconsistency in MethodNode, which can be exploited to access unexpected object fields through dot notation. This can be used to achieve arbitrary code execution at load time. While this issue may seem similar to GHSA-m7f4-hrc6-fwg3, it is actually more severe, as it relies on fewer assumptions about trusted types. This is fixed in version 12.0.0.
How severe is CVE-2025-54413?
CVE-2025-54413 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2025-54413 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-54413?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-54413 have an EU (EUVD) identifier?
Yes. CVE-2025-54413 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-22762.
When was CVE-2025-54413 published?
CVE-2025-54413 was published on 2025-07-26 and last updated on 2026-06-17.

References

Other CWE-351 vulnerabilities

Browse all CWE-351 vulnerabilities →