flask-cors vulnerabilities
A Flask extension simplifying CORS support
- Registry
- PyPI
- Latest
- 6.0.5
- License
- MIT
6 known advisories
The latest version, 6.0.5, is not affected by any of them. Projects on older versions may be.
pip install 'flask-cors>=6.0.5'Is your project on an affected flask-cors?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for flask-cors
Flask-CORS vulnerable to Improper Handling of Case Sensitivity
- Affected
- <6.0.0
- Fixed in
- 6.0.0
Flask-CORS improper regex path matching vulnerability
- Affected
- <6.0.0
- Fixed in
- 6.0.0
Flask-CORS allows for inconsistent CORS matching
- Affected
- <6.0.0
- Fixed in
- 6.0.0
Flask-CORS allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default
- Affected
- <4.0.2
- Fixed in
- 4.0.2
flask-cors vulnerable to log injection when the log level is set to debug
- Affected
- <4.0.1
- Fixed in
- 4.0.1
Flask-Cors Directory Traversal vulnerability
- Affected
- <3.0.9
- Fixed in
- 3.0.9
Is your flask-cors version vulnerable?
Which of your client projects still run an old flask-cors?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.