# OSV-2025-256: Global-buffer-overflow in QByteArray::QByteArray

> A global buffer overflow in the KDE archive library allows attackers to cause crashes or potentially execute code via malicious archives.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Apr 2025

## What is OSV-2025-256?

OSV-2025-256 is a memory corruption vulnerability in kimageformats, published on 5 Apr 2025. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=408025086

```
Crash type: Global-buffer-overflow READ 15
Crash state:
QByteArray::QByteArray
KZip::openArchive
KArchive::open
```

## Which versions are affected by OSV-2025-256?

1 open source package ship an affected version, including kimageformats.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kimageformats` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2025-256?

No fix has been published for OSV-2025-256 yet. Limit exposure of the affected software until one is available.

## Is OSV-2025-256 being exploited?

There is no known exploitation of OSV-2025-256 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2025-256 and fix it if it is affected.

What it is: OSV-2025-256 is a memory corruption vulnerability in kimageformats, published on 5 Apr 2025. 
Exploitation: There is no known exploitation of OSV-2025-256 in the wild and no public exploit code.

Affected packages and fixed versions:
- kimageformats (OSS-Fuzz): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/OSV-2025-256/ (Markdown: https://insights.sbomify.com/OSV-2025-256/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2025-256

---
From sbomify Insights: https://insights.sbomify.com/OSV-2025-256/
Summaries are generated and may contain mistakes; the official description above is the record.