CVE-2026-25541VulnerabilityPublished 8 Sep 2026Updated 10 Nov 2026

SUSE · Security update for waylyrics

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-25541· Medium 5.5

Public exploit available · CVSS 5.5 Medium · fixed in SUSE package updates : patch SUSE bytes as a priority.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 4.0 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.11.1, 1.11

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade bytes to 1.11.1; tokio-rs/bytes to 1.11.

Affected software

Product	Affected	Fixed in
tokio-rsbytes	Affected >=1.2.1 <1.11.1	Fixed in 1.11.1
crates.iotokio-rs/bytes`pkg:cargo/tokio-rs/bytes`Other threats	Affected >=1.2.1 <1.11	Fixed in 1.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for waylyrics fixes the following issues: Changes in waylyrics: - Update to version 0.4.0 (CVE-2026-25541 bsc#1274106) * Added plugin architecture and SakuraLLM translation plugin * Added OpenCC support for Simplified/Traditional Chinese * Added support for custom CSS themes and style presets * Added auto theme switching based on light/dark mode * Added shortcut keys for decoration, passthrough, and search * Improved MPRIS and SMTC audio player integration * Improved TOML config handling and automatic comment updates * Optimized lyric search, fetch speed, and UI responsiveness * Fixed window passthrough state and click-through toggles * Updated dependencies and bumped MSRV requirement - Update to version 0.3.21: * docs: update changelog [ci skip] * chore: bump version to v0.3.21 * build: bump dependencies * build(deps): bump tokio from 1.43.0 to 1.43.1 * build(deps): bump openssl from 0.10.71 to 0.10.72 * build(deps): bump rust_decimal from 1.36.0 to 1.37.1 * build(deps): bump async-trait from 0.1.86 to 0.1.88 * build(deps): bump reqwest from 0.12.12 to 0.12.15 * build(deps): bump rust_decimal_macros from 1.36.0 to 1.37.1 * build(deps): bump the serde group with 2 updates * fix:.一个错误 * fix: 手动刷新歌词时清空歌词标签缓存 * style: :lipstick: cargo fmt * perf: DashMap 作为歌词标签存在性缓存 * feat: 添加对从音乐文件元数据读取歌词的支持 * build(deps): bump ring from 0.17.11 to 0.17.13 (#303) * chore: add script to export dup deps [ci skip] * fix(CI): remove outdated test of qqmusic api initialization [ci skip] * build: bump dependencies * docs(readme): HotLyric, alternative on windows [ci skip] * docs(readme): note on project status * build(deps): bump openssl from 0.10.68 to 0.10.70 (#301) * build(deps): bump serde_json from 1.0.134 to 1.0.138 in the serde group (#296) * build(deps): bump thiserror from 2.0.9 to 2.0.11 (#297) * build(deps): bump tokio from 1.42.0 to 1.43.0 (#298) * build(deps): bump futures-lite from 2.5.0 to 2.6.0 (#299) * build(deps): bump windows from 0.58.0 to 0.59.0 (#300) * build(deps): bump dark-light to 2.0.0 * build(deps): bump reqwest from 0.12.9 to 0.12.12 (#291) * build(deps): bump the serde group with 2 updates (#290) * build(deps): bump gdk4-win32 from 0.9.3 to 0.9.5 (#292) * build(deps): bump thiserror from 2.0.6 to 2.0.9 (#293) * build(deps): bump glib-macros from 0.20.5 to 0.20.7 (#294) * rust version problem (#289) * enhance: switch to better tray-icon implementation for windows [ci skip] * build: migrate to ksni 0.3 * chore: dedup code * chore: fix deepsource lints * refactor: extract set_by_mode * ci: add .deepsource.toml * docs(readme): add introduction [ci skip] * docs(readme): add alternative `lyric-for-musixfox` [ci skip] * docs(readme): add preview images [ci skip] * docs(readme): replace text with logos * docs: update changelog & metainfo * chore: release v0.3.20 * enhance: comment for sub table in config * log: capture panics * fix: check if instance name used * docs: update metainfo & changelog * hotfix: build on windows * chore: release v0.3.19 * chore(deps): bump dependencies * build(deps): bump the serde group with 2 updates (#280) * build(deps): bump tracing from 0.1.40 to 0.1.41 (#281) * build(deps): bump tray-icon from 0.19.1 to 0.19.2 (#282) * build(deps): bump rfd from 0.15.0 to 0.15.1 (#284) * build(deps): bump url from 2.5.3 to 2.5.4 (#283) * docs(build): check MSRV * chore(clippy): fix clippy warnings * chore: update lock file * fix: setCookies for QQMusicApi * fix: instance format * feat: support multi-monitor setup (#278) * feat: Implement color-scheme autoswitch (light/dark mode) (#277) * enhance: unregister latest theme * build(deps): bump rustls from 0.23.16 to 0.23.18 (#276) * fix: LazyLock is not stable yet in 1.73 rustc * chore: fix details URL in metainfo * chore: bump version to 0.3.18 * test: search/query via lrclib * feat: support LRCLib provider * chore: apply clippy fix * fix: `login_qqmusic` call was not awaited * chore(deps): bump dependencies * feat: show errors from providers in search_window * fix: search failure dialog cannot be spawned outside GTK thread * docs: fix typo in filename * docs(i18n): translation for contribution.md and build guide ubuntu (#272) * fix: add artists to QQMusic keyword * fix(test): initialize QQMusic * feat: set cookies for QQMusicApi in config * chore: migrate to qqmusic-rs 0.2.0 * enhance: init lyric provider with any struct * build(deps): bump the serde group with 2 updates (#266) * build(deps): bump glib-macros from 0.20.4 to 0.20.5 (#267) * build(deps): bump thiserror from 1.0.64 to 1.0.66 (#268) * build(deps): bump regex from 1.11.0 to 1.11.1 (#269) * build(deps): bump tray-icon from 0.19.0 to 0.19.1 (#270) * chore: support nix flake (#264) * fix: set text wrap to show very-long lyric * docs(readme): add alternative `lyrica` * ch

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews

Related threats