# CVE-2026-1998: micropython runtime.c mp_import_all memory corruption

> A local attacker can exploit memory corruption in MicroPython's import function to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 6 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-1998, GHSA-p2vv-8mpq-57x2, UBUNTU-CVE-2026-1998, openSUSE-SU-2026:10156-1, openSUSE-SU-2026:20199-1

## What is CVE-2026-1998?

CVE-2026-1998 is a medium-severity memory corruption vulnerability in micropython, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in micropython up to 1.27.0. This vulnerability affects the function mp_import_all of the file py/runtime.c. This manipulation causes memory corruption. The attack needs to be launched locally. The exploit has been published and may be used. Patch name: 570744d06c5ba9dba59b4c3f432ca4f0abd396b6. It is suggested to install a patch to address this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-1998?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `micropython` | openSUSE:Leap 16.0 | All versions | 1.26.1-bp160.1.1 |
| `micropython` | openSUSE:Tumbleweed | All versions | 1.26.1-2.1 |

Products: Micropython Micropython.

## How do I fix CVE-2026-1998?

Apply the vendor's patch.

## Is CVE-2026-1998 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1998 exists.

## Other vulnerabilities in micropython

- [CVE-2023-7158](https://insights.sbomify.com/CVE-2023-7158/): MicroPython objslice.c slice_indices heap-based overflow (high 7.3)
- [CVE-2024-8946](https://insights.sbomify.com/CVE-2024-8946/): MicroPython VFS Unmount vfs.c mp_vfs_umount heap-based overflow (medium 6.9)
- [CVE-2024-8948](https://insights.sbomify.com/CVE-2024-8948/): MicroPython objint.c mpz_as_bytes heap-based overflow (medium 6.9)
- [CVE-2024-8947](https://insights.sbomify.com/CVE-2024-8947/): MicroPython objarray.c use after free (medium 6.3)
- [CVE-2023-7152](https://insights.sbomify.com/CVE-2023-7152/): MicroPython modselect.c poll_set_add_fd use after free (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1998 and fix it if it is affected.

What it is: CVE-2026-1998 is a medium-severity memory corruption vulnerability in micropython, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1998 exists.

Affected product: micropython. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-1998/ (Markdown: https://insights.sbomify.com/CVE-2026-1998/index.md)
```

## Sources

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

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