How severe is CVE-2018-19323?

CVE-2018-19323 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-19323?

Affected package information for CVE-2018-19323 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-19323?

No fixed release is recorded for CVE-2018-19323 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2018-19323 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2018-19323 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-19323 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2018-19323, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-19323?

CVE-2018-19323 has an EPSS (Exploit Prediction Scoring System) score of 8.4%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2018-19323 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-19323 (GIGABYTE Multiple Products Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-10-24. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-11-14. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2018-19323 published, and has it been updated?

CVE-2018-19323 was published on December 21, 2018 and was last updated on October 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2018-19323

CRITICAL

CVE-2018-19323 is a critical-severity (CVSS 9.8) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-10-24) and has been used in ransomware campaigns — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08 exposes functionality…

Published

Dec 21, 2018

Updated

Oct 1, 2026

Affected

4 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-10-24 — including use in ransomware campaigns. Federal agencies were required to remediate by 2022-11-14.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2018-19323.

EPSS Exploitation Probability

via FIRST.org ↗

8.4%probability of exploitation in next 30 days

Lower Risk+0.54%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-19323 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08 exposes functionality to read and write Machine Specific Registers (MSRs).

Affected Products

4 products · 4 configurations

Application

aorus graphics enginegigabyte

< 1.57

range

Application

gigabyte app centergigabyte

≤ 1.05.21

range

Application

oc guru iigigabyte

1 version

2.08

Application

xtreme gaming enginegigabyte

< 1.26

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, A…

secureauth.comNVDMay 2020

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, A…

seclists.orgNVDMay 2020

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, A…

cisa.govCISAOct 2022

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, A…

cisa.govAPIDec 2021

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2018-19323 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-19323 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2018-19323

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2018-19323 in your dependencies?