# Flask-Cors Directory Traversal vulnerability

Advisory record · `GHSA-xc3p-ff3m-f46v`

- **Identifiers:** `GHSA-xc3p-ff3m-f46v` · `CVE-2020-25032` · `PYSEC-2020-43`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 6 May 2021
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 May 2021, 18:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `flask-cors` (PyPI): affected `<3.0.9`; fixed in `3.0.9`

## Machine-written summary

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

> Flask-CORS before 3.0.9 is vulnerable to directory traversal, because resource matching does not require pathnames to be in a canonical form. An attacker who can send requests to an affected application can use "../" sequences to reach private resources. Upgrade flask-cors to version 3.0.9 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.039, the 90th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:37 UTC: First seen by agentprime
- 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xc3p-ff3m-f46v)

## Sources

- [GitHub Advisory Database: GHSA-xc3p-ff3m-f46v](https://github.com/advisories/GHSA-xc3p-ff3m-f46v)
- [OSV: GHSA-xc3p-ff3m-f46v](https://osv.dev/vulnerability/GHSA-xc3p-ff3m-f46v)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-25032>
- <https://github.com/corydolphin/flask-cors/commit/67c4b2cc98ae87cf1fa7df4f97fd81b40c79b895>
- <https://github.com/advisories/GHSA-xc3p-ff3m-f46v>
- <https://github.com/corydolphin/flask-cors>
- <https://github.com/corydolphin/flask-cors/releases/tag/3.0.9>
- <https://github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2020-43.yaml>
- <https://www.debian.org/security/2020/dsa-4775>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00028.html>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00032.html>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00039.html>
- <http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00048.html>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xc3p-ff3m-f46v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xc3p-ff3m-f46v/>. Everything for agents: <https://agentprime.io/llms.txt>.
