In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the
Source GCVE Database
Not known to be exploited · CVSS 3.2 Low : upgrade to 25.08.0 when convenient.
Data as of 19 Nov 2026, 02:29 UTC
Thin evidence
One scorer or none| CNA (mitre) | CVSS 3.1 | 3.2 |
|---|
- Patch
- Available – fixed in 25.08.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade kde/skanpage to 25.08.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkde/skanpagepkg:github/kde/skanpageOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in KDE Skanpage version 25.08.0 and later. Users should upgrade to version 25.08.0 or newer to resolve this issue. No other mitigation actions are indicated.
Description
KDE Skanpage versions before 25.08.0 have a vulnerability where an attempt to overwrite a file may result in the new file containing the new content at the beginning followed by partial old content at the end. This occurs due to incorrect use of QIODevice::ReadWrite instead of QIODevice::WriteOnly.