<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: flask-cors project</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-6866: corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case-insensiti</title><link>https://patchthecve.com/cve/CVE-2024-6866.html</link><guid>https://patchthecve.com/cve/CVE-2024-6866.html</guid><pubDate>Wed, 17 Jun 2026 08:18:52 +0000</pubDate><description>HIGH 7.5: corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case-insensitive due to the use of the `try_match` function, which is originally intended for matching hosts. This results in a mismatch because paths in URLs are case-sensitive, but the regex matching tr</description></item><item><title>CVE-2024-6844: A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handl</title><link>https://patchthecve.com/cve/CVE-2024-6844.html</link><guid>https://patchthecve.com/cve/CVE-2024-6844.html</guid><pubDate>Wed, 17 Jun 2026 08:18:49 +0000</pubDate><description>MEDIUM 5.3: A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the &#x27;+&#x27; character in URL paths. The request.path is passed through the unquote_plus function, which converts the &#x27;+&#x27; character to a space &#x27; &#x27;. This behavior leads to incorrect path no</description></item><item><title>CVE-2024-6839: corydolphin/flask-cors version 4.0.1 contains an improper regex path matching vulnerability</title><link>https://patchthecve.com/cve/CVE-2024-6839.html</link><guid>https://patchthecve.com/cve/CVE-2024-6839.html</guid><pubDate>Wed, 17 Jun 2026 08:18:48 +0000</pubDate><description>MEDIUM 5.3: corydolphin/flask-cors version 4.0.1 contains an improper regex path matching vulnerability. The plugin prioritizes longer regex patterns over more specific ones when matching paths, which can lead to less restrictive CORS policies being applied to sensitive endpoints. This mismatch in regex pattern</description></item></channel></rss>