VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

espeak-ruby: vulnerability history, versions and safety

espeak-ruby is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 5 releases, from Oct 2017 to Aug 2018. 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 C1 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 espeak-ruby vulnerabilities

Vulert verdict on espeak-ruby 1.1.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 1.1.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 21 Aug 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 48 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 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 espeak-ruby, 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
1.1.0 24 Sep 2022 none MIT — Details →
1.0.5 30 Nov 2021 none MIT — Details →
1.0.4 01 Feb 2017 none MIT — Details →
1.0.3 14 May 2016 none MIT — Details →
1.0.2 24 Feb 2015 C1 H1 MIT Yes Details →
1.0.1 16 Jan 2014 C1 H1 — Yes Details →
1.0.0 12 Jan 2014 C1 H1 — Yes Details →
0.4.0 17 Apr 2012 C1 H1 — Yes Details →
0.3.0 09 Oct 2009 C1 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for espeak-ruby

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10193: Arbitrary Command Execution in espeak-ruby 9.8 critical 1.0.3 24 Oct 2017
High severity vulnerability in espeak-ruby gem N/A high 1.0.3 21 Aug 2018

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 espeak-ruby

Is espeak-ruby safe to use?

Vulert records 2 vulnerabilities for espeak-ruby in RubyGems: 1 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 espeak-ruby's Vulert package health score?

Vulert scores espeak-ruby 76/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 espeak-ruby affected?

No. 1.1.0, 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 espeak-ruby should I use?

1.1.0 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 espeak-ruby have?

2 vulnerabilities are recorded for espeak-ruby in the RubyGems ecosystem: 1 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 espeak-ruby vulnerabilities disclosed?

0 vulnerabilities were recorded for espeak-ruby in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 espeak-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 espeak-ruby for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the espeak-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.