CVE-2026-1998 json
micropython runtime.c mp_import_all memory corruption
published 9mo ago modified 4mo ago also EUVD-2026-5694
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- micropython openSUSE Leap 16.0 1.26.1-bp160.1.1
- micropython openSUSE Tumbleweed 1.26.1-2.1
opensuse advisories openSUSE-SU-2026:20199-1openSUSE-SU-2026:10156-1
Is CVE-2026-1998 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-1998 updated cvss 5.5
micropython: micropython runtime.c mp_import_all memory corruption
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/micropython/micropython/pull/18671 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/micropython/micropython/issues/18639#issue-3780651410 referenced PoC, tagged "exploit" by a source, unverified
- vuldb.com https://vuldb.com/?submit.743396 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/micropython/micropython/issues/18639 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:OF/RC:C |
| CNA | 4.0 | 1.9 | 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 2.0 | 1.7 | AV:L/AC:L/Au:S/C:N/I:N/A:P |
Affected products
- n/a micropython
Classification
References
-
github.com
/micropython/micropython/pull/18671
issue-tracking, exploit
-
github.com
/dpgeorge/micropython/commit/570744d06c5ba9dba59b4c3f432ca4f0abd396b6
patch
-
github.com
/micropython/micropython/issues/18639#issue-3780651410
exploit, issue-tracking
-
vuldb.com
/?submit.743396
third-party-advisory, exploit, vdb-entry
-
github.com
/micropython/micropython/issues/18639
issue-tracking, exploit
-
vuldb.com
/?id.344546
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.344546
signature, permissions-required, vdb-entry
-
github.com
/micropython/micropython/
product
Sources
- CVE List CVE-2026-1998
- NVD CVE-2026-1998
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.