Summary
Quart leaks raw request body (incl. plaintext passwords) to stdout via stray debug print in Body.await
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.get_data(), WTForms validate_on_submit(), 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:
python data = bytearray() while not self._queue.empty(): data.extend(self._queue.get_nowait()) print(data) # <-- not present in 0.22.0 if ( self._max_content_length is not None and len(data) > self._max_content_length ): raise RequestEntityTooLarge()
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.get_json(), file uploads, etc.).
PoC
pip install quart==0.23.0(requires Python 3.13+)- Minimal route:
python @app.route("/login", methods=["POST"]) async def login(): form_data = await request.form ... - Submit a POST with form data, e.g. a login form with
staff_id/passwordfields. - Observe stdout: the full raw body is printed as
bytearray(b'csrf_token=...&staff_id=...&password=...').
Confirmed via source diff against 0.22.0's request.py, where this line does not exist.
Impact
Any app that captures stdout in logs (terminal redirect, systemd/journald, Docker logs, cloud log aggregation, etc.) will have every submitted form body, including login credentials, written to logs in plaintext. This affects any Quart 0.23.0 app handling authentication or any sensitive form data, and is trivially triggerable by any user simply submitting a form (no attacker action required beyond normal use).
GHSA-V853-P72Q-4CFW has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.23.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-V853-P72Q-4CFW? GHSA-V853-P72Q-4CFW is a high-severity security vulnerability in quart (pip), affecting versions = 0.23.0. It is fixed in 0.23.1.
- How severe is GHSA-V853-P72Q-4CFW? GHSA-V853-P72Q-4CFW has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of quart are affected by GHSA-V853-P72Q-4CFW? quart (pip) versions = 0.23.0 is affected.
- Is there a fix for GHSA-V853-P72Q-4CFW? Yes. GHSA-V853-P72Q-4CFW is fixed in 0.23.1. Upgrade to this version or later.
- Is GHSA-V853-P72Q-4CFW exploitable, and should I be worried? Whether GHSA-V853-P72Q-4CFW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-V853-P72Q-4CFW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-V853-P72Q-4CFW? Upgrade
quartto 0.23.1 or later.