VulnerabilityPublished 26 Nov 2025

CVE-2025-55174: KDE Skanpage · Incorrect Provision of Specified Functionality

Affects KDE SkanpageSource CVE Database V5

Not known to be exploited · CVSS 3.2 Low : upgrade to 25.08.0 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

3.2Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component 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 remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 kde/skanpage to 25.08.0.

Affected software

Product	Affected	Fixed in
GitHubkde/skanpage`pkg:github/kde/skanpage`Other threats	Affected <25.08.0	Fixed in 25.08.0

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

AI-suggested

Upgrade KDE Skanpage to version 25.08.0 or later as soon as it becomes available, as this version addresses the improper file overwrite handling.
If you cannot patch yet, consider restricting local access to systems running vulnerable versions of Skanpage to trusted users only, minimizing the risk of local exploitation.
Implement file integrity monitoring on scanned documents to detect unexpected residual data or corruption.
Review and audit scanning workflows to ensure sensitive documents are handled securely and residual data risks are minimized, including secure deletion or overwriting of temporary files.
Educate users about the potential for residual data in scanned files and encourage verification of scanned document contents before distribution.
For organizations with strict data protection requirements, consider alternative scanning tools that do not exhibit this vulnerability until patched.
Monitor KDE and security advisories for official patches and apply them promptly.
If feasible, contribute to or review KDE Skanpage source code to verify proper file handling practices and prevent similar issues in the future.

Description

In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial contents of the old file at the end, because of use of QIODevice::ReadWrite instead of QODevice::WriteOnly.

Impact

For European organizations, the impact of CVE-2025-55174 is generally low but not negligible. Organizations relying on KDE Skanpage for document scanning and processing may encounter files that unintentionally contain residual data from previous files, potentially leading to minor data integrity issues. While this does not directly compromise system confidentiality, integrity, or availability on a broad scale, it could cause confusion or inadvertent exposure of sensitive information if overwritten files are shared or processed further. The vulnerability requires local access and has high attack complexity, limiting the likelihood of exploitation by external attackers. However, insider threats or compromised local accounts could exploit this flaw to glean partial information from residual file data. The absence of known exploits and the low CVSS score suggest limited immediate risk, but organizations with strict data handling policies or regulatory compliance requirements (e.g., GDPR) should consider the potential implications of residual data exposure. Overall, the threat is more relevant to environments with KDE Skanpage deployed on Linux workstations used for sensitive scanning tasks.

Summary

CVE-2025-55174 is a vulnerability identified in KDE Skanpage, a scanning application commonly used in Linux environments, particularly within KDE desktop ecosystems. The flaw arises from incorrect use of the Qt framework's file I/O modes: specifically, the application uses QIODevice::ReadWrite instead of QIODevice::WriteOnly when overwriting files. This improper mode causes the new file to be written starting correctly but leaves residual data from the previous file appended at the end. This behavior constitutes an incorrect provision of specified functionality (CWE-684), potentially leading to partial data leakage or corruption in the overwritten files. The vulnerability is local in nature, requiring the attacker to have local access to the system, and has a high attack complexity, meaning exploitation is not straightforward. No privileges or user interaction are required, and the vulnerability affects all versions of KDE Skanpage prior to 25.08.0. The CVSS v3.1 score is 3.2, reflecting low severity primarily due to limited confidentiality impact and no effect on integrity or availability. No known exploits have been reported in the wild, and no official patches have been linked at the time of publication. The issue is primarily a data integrity concern, where files may contain unintended leftover data, which could cause confusion or minor information disclosure if sensitive data persists in overwritten files. This vulnerability highlights the importance of correct file handling modes in software development to prevent subtle data leakage or corruption issues.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Dec 2025, 06:23 UTC

WeaknessesCWE-684

Technical details

References

Community reviews

Related threats