Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

PYSEC-2023-259

CVE-2023-7152

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI micropython-os

    Affected
    every version
    Fixed in
    no fixed version recorded

  • PyPI micropython-select

    Affected
    every version
    Fixed in
    no fixed version recorded

  • PyPI micropython-copy

    Affected
    every version
    Fixed in
    no fixed version recorded

  • PyPI micropython-io

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2023-7152: 0.89% estimated exploitation activity in the next 30 days; percentile 59.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A vulnerability, which was classified as critical, has been found in MicroPython 1.21.0/1.22.0-preview. Affected by this issue is the function poll_set_add_fd of the file extmod/modselect.c. The manipulation leads to use after free. The exploit has been disclosed to the public and may be used. The patch is identified as 8b24aa36ba978eafc6114b6798b47b7bfecdca26. It is recommended to apply a patch to fix this issue. VDB-249158 is the identifier assigned to this vulnerability.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from osv record PYSEC-2023-259

  2. Revision 3 · amended ·

    Amended from osv record PYSEC-2023-258

  3. Revision 2 · amended ·

    Amended from osv record PYSEC-2023-257

  4. Revision 1 · created ·

    Published from osv record PYSEC-2023-256

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-7152

Advisory: PYSEC-2023-259
IDs: CVE-2023-7152
Record: https://patchnext.com/advisories/cve-2023-7152 (revision 4, source checked 24 Oct 2026, 04:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI micropython-os: affected every version
- PyPI micropython-select: affected every version
- PyPI micropython-copy: affected every version
- PyPI micropython-io: affected every version

## Suggested inspection (read-only)
- `python -m pip show micropython-os`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show micropython-select`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show micropython-copy`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show micropython-io`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on micropython-os, micropython-select, micropython-copy, micropython-io.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2023-256 (OSV record PYSEC-2023-256 lists affected ranges: PyPI micropython-copy >=0)
- Verified: https://osv.dev/vulnerability/PYSEC-2023-257 (OSV record PYSEC-2023-257 lists affected ranges: PyPI micropython-io >=0)
- Verified: https://osv.dev/vulnerability/PYSEC-2023-258 (OSV record PYSEC-2023-258 lists affected ranges: PyPI micropython-os >=0)
- Verified: https://osv.dev/vulnerability/PYSEC-2023-259 (OSV record PYSEC-2023-259 lists affected ranges: PyPI micropython-select >=0)

Commands are suggestions: review each one before running it.

Loading voting…