What is CVE-2016-11086?

CVE-2016-11086 is a high-severity security vulnerability in oauth (rubygems), affecting versions < 0.5.5. It is fixed in 0.5.5.

How severe is CVE-2016-11086?

CVE-2016-11086 has a CVSS score of 7.4 (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 oauth are affected by CVE-2016-11086?

oauth (rubygems) versions < 0.5.5 is affected.

Is there a fix for CVE-2016-11086?

Yes. CVE-2016-11086 is fixed in 0.5.5. Upgrade to this version or later.

Is CVE-2016-11086 exploitable, and should I be worried?

Whether CVE-2016-11086 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-2016-11086 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-2016-11086 in oauth

Q: How severe is CVE-2016-11086?

CVE-2016-11086 has a CVSS score of 7.4 (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 oauth are affected by CVE-2016-11086?

oauth (rubygems) versions < 0.5.5 is affected.

Q: Is there a fix for CVE-2016-11086?

Yes. CVE-2016-11086 is fixed in 0.5.5. Upgrade to this version or later.

Q: Is CVE-2016-11086 exploitable, and should I be worried?

Whether CVE-2016-11086 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-2016-11086 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.

Q: How do I fix CVE-2016-11086?

Upgrade oauth to 0.5.5 or later.

Summary

Improper Certificate Validation in oauth ruby gem

lib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information.

Impact

CVE-2016-11086 has a CVSS score of 7.4 (High). The vector is network-reachable, no 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 (0.5.5); upgrading removes the vulnerable code path.

Affected versions

oauth (< 0.5.5)

Security releases

oauth → 0.5.5 (rubygems)

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

Upgrade oauth to 0.5.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2016-11086? CVE-2016-11086 is a high-severity security vulnerability in oauth (rubygems), affecting versions < 0.5.5. It is fixed in 0.5.5.
How severe is CVE-2016-11086? CVE-2016-11086 has a CVSS score of 7.4 (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 oauth are affected by CVE-2016-11086? oauth (rubygems) versions < 0.5.5 is affected.
Is there a fix for CVE-2016-11086? Yes. CVE-2016-11086 is fixed in 0.5.5. Upgrade to this version or later.
Is CVE-2016-11086 exploitable, and should I be worried? Whether CVE-2016-11086 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-2016-11086 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-2016-11086? Upgrade oauth to 0.5.5 or later.