VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

typespeed: vulnerability history, versions and safety

typespeed is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 5 affected ranges, from Jan 2003 to Dec 2007. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
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 typespeed vulnerabilities

Vulert verdict on typespeed i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 04 Dec 2007. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 4 years · 0 in the last year i
  • Latest disclosure 04 Dec 2007 i
  • Highest CVSS n/a i
  • With no published fix 0 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 0.6.4-1 (exclusive) 2
up to 0.4.4-10 (exclusive) 2
up to 0.4.4-8 (exclusive) 2
up to 0.4.4 (exclusive) 2
up to 0.4.2-2 (exclusive) 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2003 4
  • 2005 2
  • 2006 2
  • 2007 2

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

03 Vulnerabilities

Recorded vulnerabilities for typespeed

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service in typespeed package N/A unrated 0.6.4-1 04 Dec 2007
Buffer Overflow Vulnerability in Typespeed Package (CVE-2002-1389) N/A unrated 0.4.2-2 02 Jan 2003
Buffer Overflow Vulnerability in Typespeed Package (CVE-2003-0435) N/A unrated 0.4.4 24 Jul 2003
Privilege Escalation Vulnerability in Typespeed Package N/A unrated 0.4.4-8 16 Feb 2005
Buffer Overflow Vulnerability in Typespeed Package: CVE-2006-1515 N/A unrated 0.4.4-10 31 May 2006

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 typespeed

Is typespeed safe to use?

Vulert records 10 vulnerabilities for typespeed in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does typespeed have?

10 vulnerabilities are recorded for typespeed in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 typespeed vulnerabilities disclosed?

0 vulnerabilities were recorded for typespeed in the last 12 months, and the oldest entry in this database dates to 02 Jan 2003. 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 typespeed 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 typespeed for upcoming vulnerabilities?

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