# bundler (RubyGems) vulnerabilities 5 known vulnerabilities (1 medium), with the versions each affects and the releases that fix them. ## At a glance - Latest release: not known (cve.now hasn't read this package's releases) - Newest unaffected release: not known without release data - Registry: https://rubygems.org/gems/bundler ## Advisories (5) ### [CVE-2021-43809](https://cve.now/CVE-2021-43809): Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile - Severity: Medium 6.7 - Published: Dec 8, 2021 - Affected: fixed in 2.2.33. ### [CVE-2020-36327](https://cve.now/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 - Severity: Unrated - Published: Apr 29, 2021 - Affected: from 1.16.0, fixed in 2.2.10; from 2.2.11, fixed in 2.2.18. ### [CVE-2019-3881](https://cve.now/CVE-2019-3881): Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations… - Severity: Unrated - Published: Sep 4, 2020 - Affected: from 1.14.0, fixed in 2.1.0. ### [CVE-2016-7954](https://cve.now/CVE-2016-7954): Bundler 1.x might allow remote attackers to inject arbitrary Ruby code into an application by leveraging a gem name collision on a… - Severity: Unrated - Published: Dec 22, 2016 - Affected: from 1.0.0, fixed in 2.0.0. ### [CVE-2013-0334](https://cve.now/CVE-2013-0334): Bundler before 1.7, when multiple top-level source lines are used, allows remote attackers to install arbitrary gems by creating a gem… - Severity: Unrated - Published: Oct 31, 2014 - Affected: fixed in 1.7.0. --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/packages/rubygems/bundler Site guide for agents: https://cve.now/llms.txt Uses NVD data; not endorsed by NVD.