Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2020-26244 — oic

MEDIUMFix: OpenIDC/pyoidc@62f8d75

CVE-2020-26244 is a medium-severity (CVSS 6.8) CWE-325 vulnerability in oic. A fix is available for oic — see the affected versions and patch details below.

Multiple cryptographic issues in Python oic

Also known asGHSA-4fjv-pmhg-3rfgPYSEC-2020-69
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 10, 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 CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.44%0.89%1.33%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

CVE-2020-26244 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍oic

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

Impact

  • Client implementations using this library

Issues

  1. The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.
  2. JWA none algorithm was allowed in all flows.
  3. oic.consumer.Consumer.parse_authz returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.
  4. iat claim was not checked for sanity (i.e. it could be in the future)

Patches

  1. IdToken signature is now always checked.
  2. JWA none algorithm is now allowed only if using the response_type code
  3. IdToken verification is now done automatically.
  4. iat claim is now checked for sanity.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIoicall versions1.2.1pip install --upgrade 'oic==1.2.1'

Affected Products

1 product · 1 configurations
Application
python openid connectpython_openid_connect_project
< 1.2.1
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 oic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update oic to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-26244 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact * Client implementations using this library ### Issues 1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg. 2) JWA `none` algorithm was allowed in all flows. 3) `oic.consumer.Consumer.parse_authz` returns an unverified IdToken. The verification of the token was left to the discretion of the implementator. 4) `iat` claim was not checked for sanity (i.e. it could be in the future) ### Patches 1) IdToken signature is now always checked. 2) JWA `none` algorithm is now allowed only if using the `response_type` `c
O3 Security · Impact-Aware SCA

Is CVE-2020-26244 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-26244: oic — Fixed in 1.2.1