CVE-2019-1125

MEDIUMNVD 5.65.5▼
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 5.6; sources differ by 0.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 5%CVSS: 5.6Exploit: NoneExposed: 0

A fix is available — apply it.

An information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory. An attacker who successfully exploited the vulnerability could read privileged data across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information that could be used to try to compromise the affected system further. On January 3, 2018, Microsoft released an advisory and security updates related to a newly-discovered class of hardware vulnerabilities (known as Spectre) involving speculative execution side channels that affect AMD, ARM, and Intel CPUs to varying degrees. This vulnerability, released on August 6, 2019, is a variant of the Spectre Variant 1 speculative execution side channel vulnerability and has been assigned CVE-2019-1125. Microsoft released a security update on July 9, 2019 that addresses the vulnerability through a software change that mitigates how the CPU speculatively accesses memory. Note that this vulnerability does not require a microcode update from your device OEM.

CVSS v3
5.6
EG Score
5.5(medium)
EPSS
90.4%
KEV
Not listed

Published

September 3, 2019

Last Modified

February 20, 2026

References (34)

Vendor Advisories for CVE-2019-1125(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-virtual-hwe-16.04 (4.15.0.58.79) @ xenial2026-05-27ubuntu
ubuntulinux-image-virtual-lts-xenial (4.4.0.159.140) @ trusty2026-05-27ubuntu
ubuntulinux-image-virtual (5.0.0.25.26) @ disco2026-05-27ubuntu
ubuntulinux-image-aws-hwe (4.15.0.1045.45) @ xenial2026-05-27ubuntu
ubuntulinux-image-virtual-lts-xenial (4.4.0.159.167) @ xenial2026-05-27ubuntu
redhatredhat-virtualization-host-0:4.2-20191022.0.el7_62019-10-30redhat
redhatkernel-0:3.10.0-957.38.1.el72019-10-29redhat
redhatredhat-virtualization-host-0:4.3.6-20190924.0.el7_72019-10-10redhat
redhatkernel-0:3.10.0-862.43.1.el72019-10-08redhat
redhatkernel-0:3.10.0-514.69.1.el72019-09-25redhat
redhatkernel-0:3.10.0-327.82.1.el72019-09-25redhat
redhatkernel-0:3.10.0-693.58.1.el72019-09-12redhat
redhatkernel-rt-1:3.10.0-693.58.1.rt56.652.el6rt2019-09-11redhat
redhatkernel-0:2.6.32-431.96.1.el62019-09-10redhat
redhatkernel-rt-0:3.10.0-1062.1.1.rt56.1024.el72019-09-04redhat
redhatkernel-0:3.10.0-1062.1.1.el72019-09-04redhat
redhatkernel-0:2.6.32-504.80.2.el62019-08-13redhat
redhatkernel-0:2.6.32-754.18.2.el62019-08-13redhat
redhatkernel-rt-0:4.18.0-80.7.2.rt9.154.el8_02019-08-07redhat
redhatkernel-0:4.18.0-80.7.2.el8_02019-08-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:43 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-05 02:27 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-03 00:35 UTCOSV refresh
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 42 more
  1. 2026-06-19 19:23 UTCEPSS rescore
  2. 2026-06-19 19:23 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-16 17:50 UTCEPSS rescore
  6. 2026-06-15 17:45 UTCEPSS rescore
  7. 2026-06-14 23:15 UTCEPSS rescore
  8. 2026-06-14 23:15 UTCEPSS rescore
  9. 2026-06-14 19:13 UTCOSV refresh
  10. 2026-06-13 22:58 UTCEPSS rescore
  11. 2026-06-12 23:09 UTCEPSS rescore
  12. 2026-06-11 13:58 UTCEPSS rescore
  13. 2026-06-10 22:16 UTCEPSS rescore
  14. 2026-06-10 13:19 UTCEPSS rescore
  15. 2026-06-08 14:15 UTCEPSS rescore
  16. 2026-06-07 15:23 UTCEPSS rescore
  17. 2026-06-07 15:23 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-04 13:10 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-01 13:50 UTCEPSS rescore
  29. 2026-06-01 13:50 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-31 00:14 UTCEPSS rescore
  34. 2026-05-29 13:42 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-27 15:00 UTCEG score recompute
  37. 2026-05-27 15:00 UTCVendor advisory
  38. 2026-05-27 15:00 UTCGHSA enrichment
  39. 2026-05-27 13:38 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore
  42. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48071
    First seen Jan 27, 2020

    Microsoft Windows Kernel - Information Disclosure

    Open source ↗
  • GitHub PoCbitdefender/swapgs-attack-poc
    First seen Jan 27, 2020

    This repository contains the sources and documentation for the SWAPGS attack PoC (CVE-2019-1125)

    Open source ↗

Frequently asked(5)

What is CVE-2019-1125?
CVE-2019-1125 is a medium vulnerability published on September 3, 2019. An information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory. An attacker who successfully exploited the vulnerability could read privileged data across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an…
When was CVE-2019-1125 disclosed?
CVE-2019-1125 was first published in the National Vulnerability Database on September 3, 2019, with the most recent update on February 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1125 actively exploited?
CVE-2019-1125 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-1125?
CVE-2019-1125 has a CVSS v3 base score of 5.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.5.
How do I remediate CVE-2019-1125?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1125, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-1125

Explore →

Is Your Infrastructure Affected by CVE-2019-1125?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs