CVE-2019-25022: An issue was discovered in Scytl sVote 2.1

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2019-25022 is a critical-severity flaw (CVSS 9.8) affecting secure vote. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Scytl sVote 2.1. An attacker can inject code that gets executed by creating an election-event and injecting a payload over an event alias, because the application calls Runtime.getRuntime().exec() without validation.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Weakness	CWE-78
Published	2021-02-27
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: scytl

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

Am I affected?

Timeline

2021-02-27 05:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

scytl secure vote DOWNGRADE

Affected: 2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1

1. Check installed version

apt-cache policy secure-vote || rpm -q secure-vote || secure-vote --version

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

apt-cache madison secure-vote sudo apt install secure-vote=<VERSION_BEFORE_2.1> sudo apt-mark hold secure-vote

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

dnf --showduplicates list secure-vote sudo dnf downgrade secure-vote-<VERSION_BEFORE_2.1> sudo dnf versionlock add secure-vote

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-25022?

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

Is CVE-2019-25022 being exploited?

CVE-2019-25022 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-25022 affect?

CVE-2019-25022 affects secure vote. Severity is critical (CVSS 9.8). An issue was discovered in Scytl sVote 2.1. An attacker can inject code that gets executed by creating an election-event and injecting a payload over an event alias, because the application calls Runtime.getRuntime().exec() without validati

How urgent is CVE-2019-25022?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-25023 MEDIUM 6.5 DOWNGRADE An issue was discovered in Scytl sVote 2.1
CVE-2019-25021 HIGH 7.5 DOWNGRADE An issue was discovered in Scytl sVote 2.1
CVE-2019-25020 HIGH 7.5 DOWNGRADE An issue was discovered in Scytl sVote 2.1

References

← Back to latest CVEs