Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Quart leaks raw request body (incl. plaintext passwords) to stdout via stray debug print in Body.__await__

GHSA-v853-p72q-4cfw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (quart 0.23.1), 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 quart

    Affected
    >= 0.23.0, <= 0.23.0
    Fixed in
    0.23.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary Quart 0.23.0 contains a stray debug statement (print(data)) inside Body.await in quart/wrappers/request.py. Any request whose body is awaited — await request.form, await request.getdata(), WTForms validateonsubmit(), etc. — has its raw, unparsed body printed to stdout, including plaintext form fields such as passwords and CSRF tokens. Confirmed present in 0.23.0, confirmed absent in 0.22.0. Details In src/quart/wrappers/request.py, Body.await accumulates the request body into a bytearray: ​ This fires for every request that awaits its body — the overwhelming majority of POST/PUT routes in a typical Quart app (form submissions, JSON APIs via request.getjson(), file uploads, etc.). PoC 1. pip install quart==0.23.0 (requires Python 3.13+) 2. Minimal route: ​ 3. Submit a POST with form data, e.g. a login form with staffid/password fields. 4. Observe stdout: the full raw body is printed as bytearray(b'csrftoken=...&staffid=...&password=...'). Confirmed via source diff against…

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

    Amended from ghsa record GHSA-v853-p72q-4cfw

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-v853-p72q-4cfw

  3. Revision 2 · amended ·

    Amended from osv record GHSA-v853-p72q-4cfw

  4. Revision 1 · created ·

    Published from ghsa record GHSA-v853-p72q-4cfw

Agent brief

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

# Patch Next advisory brief: GHSA-v853-p72q-4cfw

Advisory: Quart leaks raw request body (incl. plaintext passwords) to stdout via stray debug print in Body.__await__
IDs: GHSA-v853-p72q-4cfw
Record: https://patchnext.com/advisories/ghsa-v853-p72q-4cfw (revision 4, source checked 2 Nov 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: quart 0.23.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI quart: affected >= 0.23.0, <= 0.23.0; fixed in 0.23.1

## Suggested inspection (read-only)
- `python -m pip show quart`: 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 quart.
- 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-v853-p72q-4cfw (GitHub-reviewed advisory GHSA-v853-p72q-4cfw lists affected ranges: PyPI quart >=0.23.0 <=0.23.0)
- Verified: https://osv.dev/vulnerability/GHSA-v853-p72q-4cfw (OSV record GHSA-v853-p72q-4cfw lists affected ranges: PyPI quart >=0.23.0 <0.23.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…