Skip to main content
No exploitation reportedFix available

CVE-2020-36327

No exploitation reported by the sources we read.

  • Published2021-04-29
  • Fixed in2.2.18 · 2.2.10

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application. NOTE: it is not correct to use CVE-2021-24105 for every "Dependency Confusion" issue in every product.

Timeline

dates in UTC
  1. 2021-04-2903:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-36327?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-36327?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
Bundler
BranchAffectedFixed in
2.2≥ 2.2.11, < 2.2.182.2.18
2.2≥ 1.16.0, < 2.2.102.2.10
2.2≥ 2.2.11, ≤ 2.2.16no fix published
Fedoraproject fedora
BranchAffectedFixed in
34.x= 34no fix published
Microsoft package manager configurations
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bundlerUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • bundlerUbuntu:20.04:LTSall versions · no fixed version listed
  • bundlerUbuntu:16.04:LTSall versions · no fixed version listed
  • bundlerRoot:Rubyall versions · fixed in 2.1.4.41610.1
  • rh-ruby26-rubyRed Hat:rhel_software_collections:3::el7all versions · fixed in 0:2.6.9-120.el7and 4 other packages
  • rh-ruby26-rubygem-bigdecimalRed Hat:rhel_software_collections:3::el7all versions · fixed in 0:1.4.1-120.el7
  • rh-ruby26-rubygem-bundlerRed Hat:rhel_software_collections:3::el7all versions · fixed in 0:1.17.2-120.el7
  • rh-ruby26-rubygem-did_you_meanRed Hat:rhel_software_collections:3::el7all versions · fixed in 0:1.3.0-120.el7

327 more package ranges on OSV.dev

Vendor advisories

  • CVE-2020-36327 Red Hat Product Security435 products fixed · 5 known affected

    rubygem-bundler: Dependencies of gems with explicit source may be installed from a different source

    rubygem-bundler.src as a component of CloudForms Management Engine 5 · ruby.src as a component of Logging Subsystem for Red Hat OpenShift · rubygem-bundler.src as a component of Red Hat 3scale API Management Platform 2 · +2 more

  • RHSA-2022:0708 Red Hat Product Security64 products fixed

    Red Hat Security Advisory: rh-ruby26-ruby security, bug fix, and enhancement update

  • RHSA-2022:0582 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: ruby:2.6 security update

  • RHSA-2022:0581 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: ruby:2.6 security update

  • RHSA-2022:0546 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: ruby:2.5 security update

  • RHSA-2022:0545 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: ruby:2.5 security update

7 more advisories

Full record on NVD

Fix

  1. Update Bundler to 2.2.18 · 2.2.10
  2. Vendor fix Red Hat Product Security RHSA-2022:0708 · 64 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2022:0708 · 64 productsThis issue only affects configurations where gem packages are installed from multiple sources and the source repositories are explicitly defined for at least some gems. Dependencies of those source-restricted gems may be installed form a different repository, even if the same repository provides th…

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2021-04-29
Last Modified
2026-10-08
NVD status
Modified
GitHub Advisory
GHSA-fp4w-jxhp-m23p

Frequently asked questions

What is CVE-2020-36327?

Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application. NOTE: it is not correct to use CVE-2021-24105 for every "Dependency Confusion" issue in every product.

Is CVE-2020-36327 actively exploited?

Active exploitation of CVE-2020-36327 has not been confirmed. Its EPSS score was 6.3% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-36327?

CVE-2020-36327 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running bundler? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record