Advisory record · GHSA-84pr-m4jr-85g5

flask-cors vulnerable to log injection when the log level is set to debug

CVSS 5.3 MediumEPSS 0.0057 · 47th percentile

Published by the GitHub Advisory Database at 19 Apr 2024, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flask-corsPyPI<4.0.14.0.1
Identifiers
GHSA-84pr-m4jr-85g5 · CVE-2024-1681 · PYSEC-2024-271
Weakness (CWE)
CWE-117
Published
19 Apr 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

flask-cors versions before 4.0.1 are vulnerable to log injection when the log level is set to debug. An attacker who can send a GET request to the application can include a CRLF sequence in the request path to insert fake entries into the log file, which can hide other activity or confuse log analysis tools. Upgrade to flask-cors 4.0.1 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0057, the 47th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:35 UTC First seen by agentprime
  2. 31 Oct 2026, 14:35 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.