<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T20:32:03.099355+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2024-07529</id>
    <title>bdu:2024-07529</title>
    <updated>2026-10-02T20:32:03.403118+00:00</updated>
    <content>bdu:2024-07529</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2024-07529"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-locust-cve-2024-6844</id>
    <title>BREW-locust-CVE-2024-6844 — Flask-CORS allows for inconsistent CORS matching</title>
    <updated>2026-10-02T20:32:03.403172+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: locust</p>
<p>A vulnerability in corydolphin/flask-cors version 5.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-locust-cve-2024-6844"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0896</id>
    <title>certfr-2025-avi-0896 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
    <updated>2026-10-02T20:32:03.403248+00:00</updated>
    <content>certfr-2025-avi-0896</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0896"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-257774</id>
    <title>EUVD-2026-257774</title>
    <updated>2026-10-02T20:32:03.403279+00:00</updated>
    <content>EUVD-2026-257774</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-257774"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-6844</id>
    <title>fkie_cve-2024-6844</title>
    <updated>2026-10-02T20:32:03.403302+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-6844"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8vgw-p6qm-5gr7</id>
    <title>GHSA-8vgw-p6qm-5gr7 — Flask-CORS allows for inconsistent CORS matching</title>
    <updated>2026-10-02T20:32:03.403357+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: flask-cors</p>
<p>A vulnerability in corydolphin/flask-cors version 5.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8vgw-p6qm-5gr7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-1938</id>
    <title>OESA-2025-1938 — python-Flask-Cors security update</title>
    <updated>2026-10-02T20:32:03.403410+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: python-Flask-Cors</p>
<p>A Flask extension for handling Cross Origin Resource Sharing (CORS), making cross-origin AJAX possible.

Security Fix(es):</p>
<p>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 priority allows unauthorized cross-origin access to sensitive data or functionality, potentially exposing confidential information and increasing the risk of unauthorized actions by malicious actors.(CVE-2024-6839)</p>
<p>A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the &amp;apos;+&amp;apos; character in URL paths. The request.path is passed through the unquote_plus function, which converts the &amp;apos;+&amp;apos; character to a space &amp;apos; &amp;apos;. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.(CVE-2024-6844)</p>
<p>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 mat…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-1938"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10485-1</id>
    <title>openSUSE-SU-2026:10485-1 — python311-Flask-Cors-6.0.2-1.1 on GA media</title>
    <updated>2026-10-02T20:32:03.403497+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>python311-Flask-Cors-6.0.2-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10485-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-1385</id>
    <title>PYSEC-2026-1385 — Flask-CORS allows for inconsistent CORS matching</title>
    <updated>2026-10-02T20:32:03.403528+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: flask-cors</p>
<p>A vulnerability in corydolphin/flask-cors version 5.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-1385"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-6844</id>
    <title>UBUNTU-CVE-2024-6844</title>
    <updated>2026-10-02T20:32:03.403575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: python-flask-cors, Ubuntu:22.04:LTS: python-flask-cors, Ubuntu:Pro:24.04:LTS: python-flask-cors</p>
<p>A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquote_plus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-6844"/>
  </entry>
</feed>
