cve.bz

CVE-2026-53525 weechat weechat: Observable Timing Discrepancy

7.4 highEPSS 0.4%

High (7.4) in weechat weechat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
WeeChat (Wee Enhanced Environment for Chat) is a free chat client. In versions 0.3.1 through 4.9.0, the WeeChat relay authentication uses non-constant-time string comparison functions (weechat_strcasecmp and strcmp) to verify password hashes and plaintext passwords. An attacker can exploit timing differences to extract the server-computed hash character by character, then authenticate using the correct hash without knowing the password. Version 4.9.1 fixes the issue.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-208 Observable Timing Discrepancy
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53525 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53525?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53525?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53525 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
weechat>= 0.3.4, < 4.9.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13weechatno fix listedDEBIAN-CVE-2026-53525
Debian14weechat4.9.3-1DEBIAN-CVE-2026-53525
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 3 moreweechatno fix listedUBUNTU-CVE-2026-53525
openSUSELeap 16.0weechat4.10.0-bp160.1.1openSUSE-SU-2026:21615-1
openSUSETumbleweedweechat4.10.0-1.1openSUSE-SU-2026:11481-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because remote unauthenticated attackers can bypass relay authentication to obtain unauthorized access to active chat sessions and client commands. Although the timing attack requires measuring response latency across numerous authentication attempts, a successful exploit completely undermines the security boundary of the relay service. The relay component is not activated by default and must be explicitly configured and started by the user. Systems where WeeChat is run without an active network-facing relay listener are not exposed to this issue.

Red Hat's mitigation

To mitigate this issue, restrict network access to the WeeChat relay service using firewall rules, allowing connections only from trusted hosts. Alternatively, if the WeeChat relay functionality is not required, disable it to prevent potential exploitation. Consult WeeChat documentation for specific configuration steps to disable the relay or restrict its access.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53525.

Attack patterns (CAPEC)

  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON