VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

ruby: vulnerability history, versions and safety

ruby is a package in the OSS-Fuzz ecosystem. Vulert records 6 vulnerabilities for it across 35 releases, from Oct 2022 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
6 vulnerabilities recorded H3 M3
i
4 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 04 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ruby vulnerabilities

Vulert verdict on ruby i

Updated on 23 Oct 2026

Careful: 4 of the 6 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

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

What to do: Plan around the 4 vulnerabilities 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 6 over 3 years · 1 in the last year i
  • Latest disclosure 04 Jan 2026 i
  • Highest CVSS n/a i
  • With no published fix 4 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, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for ruby

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Use-after-poison vulnerability in Ruby N/A medium No fix published 29 Oct 2022
Use-after-poison in str_new_frozen_buffer in Ruby N/A high 628e432739e1d2578d357420aa652a97eb8c2649 17 Apr 2023
Use-after-poison vulnerability in rb_gc_writebarrier in Ruby N/A high No fix published 09 Apr 2023
Use-after-poison in parser_yylex in ruby N/A high No fix published 02 Sep 2023
Heap-buffer-overflow in fill_lines in Ruby N/A medium f5c3cda7d6e9053ae5ed66e36d13e568595ff1ec 17 Nov 2023

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

Is ruby safe to use?

Vulert records 6 vulnerabilities for ruby in OSS-Fuzz: 0 critical, 3 high, 3 medium and 0 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does ruby have?

6 vulnerabilities are recorded for ruby in the OSS-Fuzz ecosystem: 0 critical, 3 high, 3 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 ruby vulnerabilities disclosed?

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

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