CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:HHigh (7.4) in weechat weechat. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| weechat | >= 0.3.4, < 4.9.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | weechat | no fix listed | DEBIAN-CVE-2026-53525 |
| Debian | 14 | weechat | 4.9.3-1 | DEBIAN-CVE-2026-53525 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 26.04:LTS and 3 more | weechat | no fix listed | UBUNTU-CVE-2026-53525 |
| openSUSE | Leap 16.0 | weechat | 4.10.0-bp160.1.1 | openSUSE-SU-2026:21615-1 |
| openSUSE | Tumbleweed | weechat | 4.10.0-1.1 | openSUSE-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 rates this Important.
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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.