# CVE-2019-25622: Paint Studio 2.17 Denial of Service via Malformed Input

> Local attackers can crash Paint Studio by providing malformed input via a text file, causing application unavailability.

- **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:** 23 Mar 2026
- **Also known as:** GHSA-fcjq-prhj-cc4c

## What is CVE-2019-25622?

CVE-2019-25622 is a medium-severity denial of service vulnerability in Pixarra Paint 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

Paint Studio 2.17 contains a denial of service vulnerability that allows local attackers to crash the application by providing malformed input through the key entry mechanism. Attackers can create a text file with a large buffer of characters and trigger the application to read it, causing the application to crash and become unavailable.

Weakness: CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input)

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

It affects 1 product.


Products: Pixarra Paint Studio.

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

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

## Is CVE-2019-25622 being exploited?

There is no known exploitation of CVE-2019-25622 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25622 is a medium-severity denial of service vulnerability in Pixarra Paint 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: There is no known exploitation of CVE-2019-25622 in the wild and no public exploit code.

Affected product: Pixarra Paint 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-25622/ (Markdown: https://insights.sbomify.com/CVE-2019-25622/index.md)
```

## Sources

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

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