How severe is CVE-2024-8947?

No CVSS score has been assigned to CVE-2024-8947 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-8947?

CVE-2024-8947 affects the following packages: micropython-copy (PyPI), micropython-io (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-8947?

The records we use list no patched version of micropython-copy for CVE-2024-8947. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

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

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

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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

Yes. There are 2 known exploit references for CVE-2024-8947, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2024-8947 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th 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-8947?

CVE-2024-8947 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2024-8947 was published on September 17, 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

CVE-2024-8947 — micropython-copy

Fix: micropython/micropython@4bed614

CVE-2024-8947 is a Use After Free vulnerability in micropython-copy. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

MicroPython objarray.c use after free

Also known asGHSA-pwwp-3q7j-9mx8PYSEC-2024-92PYSEC-2024-94

Published

Sep 17, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

See advisory

Exploits

2 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-8947.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍micropython-copy🐍micropython-io

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

A vulnerability was found in MicroPython 1.22.2. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file py/objarray.c. The manipulation leads to use after free. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 1.23.0 is able to address this issue. The identifier of the patch is 4bed614e707c0644c06e117f848fa12605c711cd. It is recommended to upgrade the affected component. In micropython objarray component, when a bytes object is resized and copied into itself, it may reference memory that has already been freed.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`micropython-copy`	all versions	No fix
🐍PyPI	`micropython-io`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

micropythonmicropython

1 version

1.22.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A vulnerability was found in MicroPython 1.22.2. It has been declared as…

github.comNVDSep 2024

Report on github.com

github.comNVDSep 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for micropython-copy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of micropython-copy for CVE-2024-8947. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-8947 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works