VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

arr-pm: vulnerability history, versions and safety

arr-pm is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 10 releases, first recorded in Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all arr-pm vulnerabilities

Vulert verdict on arr-pm 0.0.12 i

Updated on 22 Oct 2026

Good news: 0.0.12, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 75/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 0.0.12 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.0.12 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.0.12 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Sep 2022 i
  • Highest CVSS 7.0 i
  • With no published fix 0 i
  • Last release 49 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for arr-pm, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.0.12 19 Sep 2022 none Apache-2.0 — Details →
0.0.11 15 Jun 2021 H1 Apache-2.0 Yes Details →
0.0.10 14 Apr 2015 H1 Apache-2.0 Yes Details →
0.0.9 05 Feb 2014 H1 Apache-2.0 Yes Details →
0.0.8 21 Mar 2013 H1 Apache-2.0 Yes Details →
0.0.7 16 Mar 2012 H1 — Yes Details →
0.0.6 15 Mar 2012 H1 — Yes Details →
0.0.5 15 Mar 2012 H1 — Yes Details →
0.0.4 09 Mar 2012 H1 — Yes Details →
0.0.3 08 Mar 2012 H1 — Yes Details →
0.0.2 08 Mar 2012 H1 — Yes Details →

All 11 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for arr-pm

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2022-39224: arr-pm vulnerable to arbitrary shell execution when extracting or listing files contained in a malicious rpm 7.0 high 0.0.12 21 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 537001

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About arr-pm

Is arr-pm safe to use?

Vulert records 1 vulnerabilities for arr-pm in RubyGems: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is arr-pm's Vulert package health score?

Vulert scores arr-pm 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of arr-pm affected?

No. 0.0.12, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of arr-pm should I use?

0.0.12 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does arr-pm have?

1 vulnerability is recorded for arr-pm in the RubyGems ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new arr-pm vulnerabilities disclosed?

0 vulnerabilities were recorded for arr-pm in the last 12 months, and the oldest entry in this database dates to 21 Sep 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of arr-pm are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor arr-pm for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the arr-pm version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.