CVE-2019-10766: Pixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to i

This week

CRITICAL 9.8REMOTEUPGRADE

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

Pixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
Published	2019-11-19
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: pixie project

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

Am I affected?

Timeline

2019-11-19 20:15 UTCPublished CVE record published
2026-06-17 02:11 UTCUpdated Record last modified

pixie project pixie UPGRADE

Affected: >= 1.0.0 and < 1.0.3 · >= 2.0.0 and < 2.0.2

Fixed in: 1.0.3, 2.0.2

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy pixie || rpm -q pixie || pixie --version

2. UPGRADE to 1.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pixie

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pixie

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison pixie sudo apt install pixie=<VERSION_BEFORE_1.0.0> sudo apt-mark hold pixie

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pixie sudo dnf downgrade pixie-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add pixie

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

pixie: upgrade to 1.0.3, 2.0.2. Exact commands for each OS are on this page.

Is CVE-2019-10766 being exploited?

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

CVE-2019-10766 affects pixie. Severity is critical (CVSS 9.8). Pixie versions 1.0.x before 1.0.3, and 2.0.x before 2.0.2 allow SQL Injection in the limit() function due to improper sanitization.

How urgent is CVE-2019-10766?

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

Related CVEs

CVE-2017-7402 CRITICAL 9.8 DOWNGRADE Pixie 1.0.4 allows remote authenticated users to upload and execute arbitrary PHP code via the POST data in an
CVE-2017-7363 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=module&x= XSS attack.
CVE-2017-7362 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=dynamic&x= XSS attack.
CVE-2017-7361 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=publish&m=static&x= XSS attack.
CVE-2017-7360 MEDIUM 6.1 DOWNGRADE Pixie 1.0.4 allows an admin/index.php s=settings&x= XSS attack.

References

← Back to latest CVEs