VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

weechat: vulnerability history, versions and safety

weechat is a package in the Debian ecosystem. Vulert records 21 vulnerabilities for it across 33 releases, from Mar 2009 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
21 vulnerabilities recorded U21
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 18 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all weechat vulnerabilities

Vulert verdict on weechat i

Updated on 23 Oct 2026

Careful: 3 of the 21 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 21 vulnerabilities on record across 17 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 21 over 17 years · 2 in the last year i
  • Latest disclosure 18 Aug 2026 i
  • Highest CVSS 9.8 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 weechat, 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 33 of 33 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 2
  • 2011 2
  • 2012 4
  • 2017 2
  • 2020 6
  • 2021 2
  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for weechat

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Overflow and Buffer Overflow in WeeChat - CVE-2024-46613 9.8 critical No fix published 10 Nov 2024
Buffer Overflow Vulnerability in WeeChat Package (CVE-2020-9760) 9.8 critical 2.7.1-1 23 Mar 2020
Buffer Overflow Vulnerability in WeeChat IRC Mode - CVE-2020-8955 9.8 critical 2.7.1-1 12 Feb 2020
Privilege Escalation Vulnerability in WeeChat Affects Multiple Debian Versions 7.8 high 2.7.1-1 23 Mar 2020
Denial of Service Vulnerability in WeeChat - Out-of-Bounds Read via WebSocket Frame 7.5 high 3.0-1+deb11u1 05 Sep 2021

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 weechat

Is weechat safe to use?

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

How many vulnerabilities does weechat have?

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

2 vulnerabilities were recorded for weechat in the last 12 months, and the oldest entry in this database dates to 19 Mar 2009. 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 weechat 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 weechat for upcoming vulnerabilities?

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