Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.4amended

pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution

CVE-2024-27528GHSA-mhg9-mm8c-c683

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 pywasm3

    Affected
    <= 0.5.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.4 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2024-27528: 0.24% estimated exploitation activity in the next 30 days; percentile 15.25 (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.

wasm3 139076a suffers from Invalid Memory Read, leading to DoS and potential Code Execution.

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

    Amended from ghsa record GHSA-mhg9-mm8c-c683

  2. Revision 1 · created ·

    Published from osv record GHSA-mhg9-mm8c-c683

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-2024-27528

Advisory: pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution
IDs: CVE-2024-27528, GHSA-mhg9-mm8c-c683
Record: https://patchnext.com/advisories/cve-2024-27528 (revision 2, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
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 pywasm3: affected <= 0.5.0

## Suggested inspection (read-only)
- `python -m pip show pywasm3`: 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 pywasm3.
- 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/GHSA-mhg9-mm8c-c683 (OSV record GHSA-mhg9-mm8c-c683 lists affected ranges: PyPI pywasm3 >=0 <=0.5.0)
- Verified: https://github.com/advisories/GHSA-mhg9-mm8c-c683 (GitHub-reviewed advisory GHSA-mhg9-mm8c-c683 lists affected ranges: PyPI pywasm3 >=0 <=0.5.0)

Commands are suggestions: review each one before running it.

Loading voting…