CVE-2019-25621: Pixel Studio 2.17 contains a denial of service vulnerability that allows local attackers to crash the applicat

Routine

MEDIUM 6.2DOWNGRADE

CVE-2019-25621 is a medium-severity flaw (CVSS 6.2) affecting pixel studio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.2 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-807
Published	2026-03-23
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: pixarra

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-23 14:16 UTCPublished CVE record published
2026-06-17 02:32 UTCUpdated Record last modified

pixarra pixel studio DOWNGRADE

Affected: 2.17

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.17

1. Check installed version

apt-cache policy pixel-studio || rpm -q pixel-studio || pixel-studio --version

2. No fixed release: DOWNGRADE to a release before 2.17 (Debian / Ubuntu)

apt-cache madison pixel-studio sudo apt install pixel-studio=<VERSION_BEFORE_2.17> sudo apt-mark hold pixel-studio

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pixel-studio sudo dnf downgrade pixel-studio-<VERSION_BEFORE_2.17> sudo dnf versionlock add pixel-studio

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25621?

pixel studio: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-25621 being exploited?

CVE-2019-25621 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25621 affect?

CVE-2019-25621 affects pixel studio. Severity is medium (CVSS 6.2). 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 cha

How urgent is CVE-2019-25621?

Priority 29/100. Public exploit reference

References

← Back to latest CVEs