CVE-2019-25621

CVE-2019-25621 is a medium-severity vulnerability in Pixarra Pixel Studio with a CVSS 3.x base score of 6.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-807.

Key facts

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.

Frequently asked questions

What is CVE-2019-25621?
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.
How severe is CVE-2019-25621?
CVE-2019-25621 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2019-25621 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-25621?
CVE-2019-25621 affects Pixarra Pixel Studio. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-25621?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2019-25621 have an EU (EUVD) identifier?
Yes. CVE-2019-25621 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2019-19983.
When was CVE-2019-25621 published?
CVE-2019-25621 was published on 2026-03-23 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-807 vulnerabilities

Browse all CWE-807 vulnerabilities →