# CVE-2019-25621: Pixel Studio 2.17 Denial of Service via Malformed Input

> Local attackers can crash Pixel Studio by entering arbitrary characters, causing the application to become unresponsive or terminate.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-vj7p-x3wh-g79x

## What is CVE-2019-25621?

CVE-2019-25621 is a medium-severity denial of service vulnerability in Pixarra Pixel Studio, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pixel Studio 2.17 contains a denial of service vulnerability that allows local attackers to crash the application by providing malformed input through the keyboard interface. Attackers can trigger the vulnerability by entering arbitrary characters, causing the application to become unresponsive or terminate abnormally.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

## Which versions are affected by CVE-2019-25621?

It affects 1 product.


Products: Pixarra Pixel Studio.

## How do I fix CVE-2019-25621?

No fix has been published for CVE-2019-25621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25621 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25621 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25621 and fix it if it is affected.

What it is: CVE-2019-25621 is a medium-severity denial of service vulnerability in Pixarra Pixel Studio, published on 23 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25621 exists.

Affected product: Pixarra Pixel Studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2019-25621/ (Markdown: https://insights.sbomify.com/CVE-2019-25621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25621
- OSV: https://osv.dev/vulnerability/CVE-2019-25621

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