VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

yaws: vulnerability history, versions and safety

yaws is a package in the Debian ecosystem. Vulert records 18 vulnerabilities for it across 9 releases, from Jun 2005 to Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded U18
i
2 with no fix published

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

See the unfixed vulnerabilities →
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 yaws vulnerabilities

Vulert verdict on yaws i

Updated on 23 Oct 2026

Careful: 2 of the 18 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 18 vulnerabilities on record across 15 years, none in the last year.

What to do: Plan around the 2 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 18 over 15 years · 0 in the last year i
  • Latest disclosure 09 Sep 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 2 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 yaws, 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 9 of 9 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2005 2
  • 2009 2
  • 2010 2
  • 2011 2
  • 2017 2
  • 2019 4
  • 2020 4

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

03 Vulnerabilities

Recorded vulnerabilities for yaws

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical OS Command Injection Vulnerability in Yaws Web Server 9.8 critical 2.0.8+dfsg-1 09 Sep 2020
Critical XXE Injection Vulnerability in Yaws Web Server 9.8 critical 2.0.8+dfsg-1 09 Sep 2020
Remote File Disclosure Vulnerability in Yaws 1.91 7.5 high 1.91-2 07 Jul 2017
Directory Traversal Vulnerability in Yaws 1.91 - Potential File Exposure Risk 6.5 medium 1.91-2 26 Nov 2019
HTTP Proxy Vulnerability in Yaws Package: CVE-2016-1000108 6.1 medium 2.0.3-2 10 Dec 2019

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 yaws

Is yaws safe to use?

Vulert records 18 vulnerabilities for yaws in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 18 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does yaws have?

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

0 vulnerabilities were recorded for yaws in the last 12 months, and the oldest entry in this database dates to 17 Jun 2005. 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 yaws 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 yaws for upcoming vulnerabilities?

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