How severe is CVE-2024-23637?

CVE-2024-23637 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-23637?

CVE-2024-23637 affects the following packages: octoprint (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-23637?

Update octoprint to 1.10.0rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23637 is resolved across your whole dependency graph.

How do I detect CVE-2024-23637 in my PyPI dependencies?

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

How do I mitigate CVE-2024-23637 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2024-23637 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-23637 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-23637?

CVE-2024-23637 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-23637?

CVE-2024-23637 is classified as Improper Authentication (CWE-287), CWE-620 (CWE-620). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-23637 published, and has it been updated?

CVE-2024-23637 was published on January 31, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2024-23637 — octoprint

MEDIUMFix: OctoPrint/OctoPrint@1729d16

CVE-2024-23637 is a medium-severity (CVSS 4.2) Improper Authentication vulnerability in octoprint. A fix is available for octoprint — see the affected versions and patch details below.

OctoPrint Unverified Password Change via Access Control Settings

Also known asGHSA-5626-pw9c-hmjrPYSEC-2024-29

Published

Jan 31, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 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-2024-23637.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

🐍octoprint

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

Impact

OctoPrint versions up until and including 1.9.3 contain a vulnerability that allows malicious admins to change the password of other admin accounts, including their own, without having to repeat their password.

An attacker who managed to hijack an admin account might use this to lock out actual admins from their OctoPrint instance.

Patches

The vulnerability will be patched in version 1.10.0.

Workarounds

OctoPrint administrators are strongly advised to thoroughly vet who has admin access to their installation.

Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by Timothy "TK" Ruppert.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`octoprint`	all versions	1.10.0rc1`pip install --upgrade 'octoprint==1.10.0rc1'`

Affected Products

1 product · 1 configurations

Application

octoprintoctoprint

≤ 1.9.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for octoprint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update octoprint to 1.10.0rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23637 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact OctoPrint versions up until and including 1.9.3 contain a vulnerability that allows malicious admins to change the password of other admin accounts, including their own, without having to repeat their password. An attacker who managed to hijack an admin account might use this to lock out actual admins from their OctoPrint instance. ### Patches The vulnerability will be patched in version 1.10.0. ### Workarounds OctoPrint administrators are strongly advised to thoroughly vet who has admin access to their installation. ### Credits This vulnerability was discovered and responsi