Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Mesop Affected by Unauthenticated Remote Code Execution via Test Suite Route /exec-py

CVE-2026-33057GHSA-gjgx-rvqr-6w6v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mesop 1.2.3), redeploy, then verify what is actually installed.

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 mesop

    Affected
    <= 1.2.2
    Fixed in
    1.2.3

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-2026-33057: 5.29% estimated exploitation activity in the next 30 days; percentile 92.59 (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.

Summary An explicit web endpoint inside the ai/ testing module infrastructure directly ingests untrusted Python code strings unconditionally without authentication measures, yielding standard Unrestricted Remote Code Execution. Any individual capable of routing HTTP logic to this server block will gain explicit host-machine command rights. Details The AI codebase package includes a lightweight debugging Flask server inside ai/sandbox/wsgiapp.py. The /exec-py route accepts base64 encoded raw string payloads inside the code parameter natively evaluated by a basic POST web request. It saves it rapidly to the operating system logic path and injects it recursively using executemodule(modulepath...). PoC Impact This presents trivial severity for systems publicly exposed or lacking strictly verified boundary firewalls due to absolute unauthenticated command injection privileges targeting the direct execution interpreter running this service sandbox.

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

    Amended from ghsa record GHSA-gjgx-rvqr-6w6v

  2. Revision 2 · amended ·

    Amended from osv record GHSA-gjgx-rvqr-6w6v

  3. Revision 1 · created ·

    Published from ghsa record GHSA-gjgx-rvqr-6w6v

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-2026-33057

Advisory: Mesop Affected by Unauthenticated Remote Code Execution via Test Suite Route /exec-py
IDs: CVE-2026-33057, GHSA-gjgx-rvqr-6w6v
Record: https://patchnext.com/advisories/cve-2026-33057 (revision 3, source checked 26 Oct 2026, 13:37 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 fix available; fixed versions by package: mesop 1.2.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mesop: affected <= 1.2.2; fixed in 1.2.3

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mesop.
- 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://github.com/advisories/GHSA-gjgx-rvqr-6w6v (GitHub-reviewed advisory GHSA-gjgx-rvqr-6w6v lists affected ranges: PyPI mesop >=0 <=1.2.2)
- Verified: https://osv.dev/vulnerability/GHSA-gjgx-rvqr-6w6v (OSV record GHSA-gjgx-rvqr-6w6v lists affected ranges: PyPI mesop >=0 <1.2.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…