CVE-2019-1010316: pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control

Q: How do I fix CVE-2019-1010316?

pyxtrlock: upgrade to newer than 0.3. Exact commands for each OS are on this page.

Q: Is CVE-2019-1010316 being exploited?

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

Q: What does CVE-2019-1010316 affect?

CVE-2019-1010316 affects pyxtrlock. Severity is high (CVSS 7.8). pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.

Routine

HIGH 7.8UPGRADE

CVE-2019-1010316 is a high-severity flaw (CVSS 7.8) affecting pyxtrlock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-284
Published	2019-07-11
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: pyxtrlock project

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

Am I affected?

Timeline

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

pyxtrlock project pyxtrlock UPGRADE

Affected: <= 0.3

Fixed in: newer than 0.3

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 0.3 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pyxtrlock

Note

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

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

pyxtrlock: upgrade to newer than 0.3. Exact commands for each OS are on this page.

Is CVE-2019-1010316 being exploited?

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

CVE-2019-1010316 affects pyxtrlock. Severity is high (CVSS 7.8). pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control. The impact is: False locking impression when run in a non-X11 session. The fixed version is: 0.4.

How urgent is CVE-2019-1010316?

Priority 33/100. High severity

References

← Back to latest CVEs