VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ruby-rmagick: vulnerability history, versions and safety

ruby-rmagick is a package in the Debian ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Oct 2023 to Jan 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded U2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 06 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ruby-rmagick vulnerabilities

Vulert verdict on ruby-rmagick i

Updated on 23 Oct 2026

Careful: one of the 2 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 2 vulnerabilities on record across 2 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 06 Jan 2026 i
  • Highest CVSS 3.3 i
  • With no published fix 1 i

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 holds for ruby-rmagick, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
6.0.1-3 U1 No Details →
6.0.1-2 U1 No Details →
6.0.1-1 U1 No Details →
5.3.0-2 U1 No Details →
5.3.0-1 U1 No Details →
4.2.3-2 U1 No Details →
4.2.3-1 U1 No Details →
2.16.0-7 U2 No Details →

Newest 8 of 8 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for ruby-rmagick

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Leak Vulnerability in ruby-magick (CVE-2023-5349): Denial of Service Risk 3.3 low No fix published 30 Oct 2023
Critical Security Update for ruby-rmagick: Addressing Vulnerability DLA-4433-1 N/A unrated 2.16.0-7+deb11u1 06 Jan 2026

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About ruby-rmagick

Is ruby-rmagick safe to use?

Vulert records 2 vulnerabilities for ruby-rmagick in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does ruby-rmagick have?

2 vulnerabilities are recorded for ruby-rmagick in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ruby-rmagick vulnerabilities disclosed?

1 vulnerability was recorded for ruby-rmagick in the last 12 months, and the oldest entry in this database dates to 30 Oct 2023. 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 ruby-rmagick 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 ruby-rmagick for upcoming vulnerabilities?

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