What is CVE-2020-26244?

CVE-2020-26244 is a high-severity security vulnerability in oic (pip), affecting versions < 1.2.1. It is fixed in 1.2.1.

How severe is CVE-2020-26244?

CVE-2020-26244 has a CVSS score of 6.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of oic are affected by CVE-2020-26244?

oic (pip) versions < 1.2.1 is affected.

Is there a fix for CVE-2020-26244?

Yes. CVE-2020-26244 is fixed in 1.2.1. Upgrade to this version or later.

Is CVE-2020-26244 exploitable, and should I be worried?

Whether CVE-2020-26244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-26244 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2020-26244 in oic

Q: How severe is CVE-2020-26244?

CVE-2020-26244 has a CVSS score of 6.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of oic are affected by CVE-2020-26244?

oic (pip) versions < 1.2.1 is affected.

Q: Is there a fix for CVE-2020-26244?

Yes. CVE-2020-26244 is fixed in 1.2.1. Upgrade to this version or later.

Q: Is CVE-2020-26244 exploitable, and should I be worried?

Whether CVE-2020-26244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-26244 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

Multiple cryptographic issues in Python oic

Issues

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

Impact

Client implementations using this library

CVE-2020-26244 has a CVSS score of 6.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.1); upgrading removes the vulnerable code path.

Affected versions

oic (< 1.2.1)

Security releases

oic → 1.2.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2020-26244? CVE-2020-26244 is a high-severity security vulnerability in oic (pip), affecting versions < 1.2.1. It is fixed in 1.2.1.
How severe is CVE-2020-26244? CVE-2020-26244 has a CVSS score of 6.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of oic are affected by CVE-2020-26244? oic (pip) versions < 1.2.1 is affected.
Is there a fix for CVE-2020-26244? Yes. CVE-2020-26244 is fixed in 1.2.1. Upgrade to this version or later.
Is CVE-2020-26244 exploitable, and should I be worried? Whether CVE-2020-26244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-26244 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-26244? Upgrade oic to 1.2.1 or later.