VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

mruby: vulnerability history, versions and safety

mruby is a package in the OSS-Fuzz ecosystem. Vulert records 78 vulnerabilities for it across 24 releases, from Jun 2020 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
78 vulnerabilities recorded H27 M36 U15
i
3 with no fix published

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

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

Most recent disclosure 31 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mruby vulnerabilities

Vulert verdict on mruby i

Updated on 23 Oct 2026

Careful: 3 of the 78 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 78 vulnerabilities on record across 6 years, 2 in the last year.

What to do: Plan around the 3 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 78 over 6 years · 2 in the last year i
  • Latest disclosure 31 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 3 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 mruby, 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 24 of 24 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 9
  • 2021 16
  • 2022 24
  • 2023 16
  • 2024 11
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for mruby

The 5 most severe of 78 vulnerabilities recorded for this package

Search all 78 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Check Failure in mruby: CheckUnwind Vulnerability N/A unrated 430e1d4f52bc98024e5a15d45c6c61efefcc1764 04 Aug 2026
UNKNOWN WRITE in udiv in mruby N/A high 8d349815309e374b545deb4d4202323c7bc5bd28 10 Jul 2022
Vulnerability in mruby: UNKNOWN READ in mrb_bint_cmp N/A medium 960021e51989881c06c7c87b2661440c1fb2a784 09 Jul 2022
Heap-buffer-overflow in udiv in mruby N/A medium e02e9ae434e462c2ff21f47c1210089951db562b 25 Jul 2022
Heap-buffer-overflow in mrb_bint_to_s in mruby N/A high 37c2f080f09390105956edb2565627f29281e24e 13 Jul 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: 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 mruby

Is mruby safe to use?

Vulert records 78 vulnerabilities for mruby in OSS-Fuzz: 0 critical, 27 high, 36 medium and 0 low, plus 15 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mruby have?

78 vulnerabilities are recorded for mruby in the OSS-Fuzz ecosystem: 0 critical, 27 high, 36 medium and 0 low, plus 15 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 mruby vulnerabilities disclosed?

2 vulnerabilities were recorded for mruby in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. 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 mruby 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 mruby for upcoming vulnerabilities?

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