NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

flask-oidc Open Redirect vulnerabilityGHSA-f9q6-69fh-4w5w

HIGHFix: puiterwijk/flask-oidc@f2ef8b4

GHSA-f9q6-69fh-4w5w is a high-severity (CVSS 7.4) Open Redirect vulnerability in flask-oidc. A fix is available for flask-oidc — see the affected versions and patch details below.

Also known asCVE-2016-1000001PYSEC-2016-25
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.44%0.88%1.32%0.2%0.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍flask-oidc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

flask-oidc version 0.1.2 and earlier is vulnerable to an open redirect.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIflask-oidcall versions1.0.0pip install --upgrade 'flask-oidc==1.0.0'

Affected Products

1 product · 1 configurations
Application
flask-oidcflask-oidc_project
≤ 0.1.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flask-oidc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update flask-oidc to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9q6-69fh-4w5w is resolved across your whole dependency graph.

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

flask-oidc version 0.1.2 and earlier is vulnerable to an open redirect.
O3 Security · Impact-Aware SCA

Is GHSA-f9q6-69fh-4w5w in your dependencies?

Find it across PyPI, including transitive dependencies.

flask-oidc Open Redirect vulnerability (High 7.4)