CVE-2019-1125

MEDIUMNVD 5.65.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.6 under NVD CVSS v3. EPSS exploit probability: 4.5% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 4.5%CVSS: 5.6Exploit: Elevated riskExposed services: Not assessed

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.6MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.5%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 3, 2019

Last Modified

February 20, 2026

References (34)

Vendor Advisories for CVE-2019-1125(2)

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 / EcosystemFix (by version range) / 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.

Affected Packages

(8 across 7 ecosystems)
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
linux3.16.36-1 ... 3.16.70-1 (66 versions)
  • every version up to 3.16.72-1: fixed in 3.16.72-1
—
linux-4.94.9.110-1~deb8u1, 4.9.144-3.1~deb8u1, 4.9.168-1~deb8u1
  • every version up to 4.9.168-1+deb9u5~deb8u1: fixed in 4.9.168-1+deb9u5~deb8u1
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.37-5, 4.19.37-5+deb10u1, 4.19.37-5+deb10u2~bpo9+1
  • every version up to 4.19.37-5+deb10u2: fixed in 4.19.37-5+deb10u2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.2.7-1: fixed in 5.2.7-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.2.7-1: fixed in 5.2.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.2.7-1: fixed in 5.2.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.2.7-1: fixed in 5.2.7-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.9.107-1 ... 4.9.88-1~bpo8+1 (50 versions)
  • every version up to 4.9.168-1+deb9u5: fixed in 4.9.168-1+deb9u5
—

Additional Vendor Advisories

(19)

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 6× in last 7d / 26× 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.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 16:37 UTCEPSS rescore
  3. 2026-10-07 23:43 UTCEPSS rescore
  4. 2026-10-06 15:12 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-03 14:22 UTCEPSS rescore
  7. 2026-09-30 14:59 UTCEPSS rescore
  8. 2026-09-30 10:08 UTCEG score recompute
  9. 2026-09-28 13:46 UTCEPSS rescore
  10. 2026-09-27 20:07 UTCOSV refresh
  11. 2026-09-27 13:40 UTCEPSS rescore
  12. 2026-09-26 15:54 UTCEPSS rescore
  13. 2026-09-26 15:54 UTCEPSS rescore
  14. 2026-09-26 00:20 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-23 13:43 UTCEPSS rescore
  17. 2026-09-22 14:43 UTCEPSS rescore
  18. 2026-09-21 20:28 UTCEPSS rescore
  19. 2026-09-20 20:10 UTCEPSS rescore
  20. 2026-09-18 19:22 UTCEPSS rescore
  21. 2026-09-17 19:22 UTCEPSS rescore
  22. 2026-09-16 14:04 UTCEPSS rescore
  23. 2026-09-15 03:05 UTCEPSS rescore
  24. 2026-09-12 14:56 UTCEPSS rescore
  25. 2026-09-11 14:48 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:32 UTCEPSS rescore
  2. 2026-09-08 04:52 UTCOSV refresh
  3. 2026-09-07 15:57 UTCEPSS rescore
  4. 2026-09-06 13:44 UTCEPSS rescore
  5. 2026-09-05 15:24 UTCEPSS rescore
  6. 2026-09-04 13:56 UTCEPSS rescore
  7. 2026-09-02 14:07 UTCEPSS rescore
  8. 2026-09-01 03:32 UTCEPSS rescore
  9. 2026-08-30 19:13 UTCEPSS rescore
  10. 2026-08-30 01:18 UTCEPSS rescore
  11. 2026-08-28 21:36 UTCEPSS rescore
  12. 2026-08-27 14:21 UTCEPSS rescore
  13. 2026-08-26 14:42 UTCEPSS rescore
  14. 2026-08-25 13:45 UTCEPSS rescore
  15. 2026-08-24 14:11 UTCEPSS rescore
  16. 2026-08-21 23:45 UTCEPSS rescore
  17. 2026-08-21 15:44 UTCOSV refresh
  18. 2026-08-20 22:51 UTCEPSS rescore
  19. 2026-08-19 17:00 UTCEPSS rescore
  20. 2026-08-18 13:44 UTCEPSS rescore
  21. 2026-08-17 13:43 UTCEPSS rescore
  22. 2026-08-16 14:52 UTCEPSS rescore
  23. 2026-08-16 02:10 UTCEPSS rescore
  24. 2026-08-15 01:26 UTCEPSS rescore
  25. 2026-08-12 13:47 UTCEPSS rescore
  26. 2026-08-09 13:43 UTCEPSS rescore
  27. 2026-08-08 16:33 UTCEPSS rescore
  28. 2026-08-07 16:23 UTCEPSS rescore
  29. 2026-08-06 13:43 UTCEPSS rescore
  30. 2026-08-06 01:21 UTCOSV refresh
  31. 2026-08-05 19:13 UTCEPSS rescore
  32. 2026-08-04 15:05 UTCEPSS rescore
  33. 2026-08-02 02:23 UTCEPSS rescore
  34. 2026-08-01 04:12 UTCEPSS rescore
  35. 2026-07-30 16:24 UTCEPSS rescore
  36. 2026-07-30 01:27 UTCEPSS rescore
  37. 2026-07-28 15:32 UTCEPSS rescore
  38. 2026-07-25 14:14 UTCEPSS rescore
  39. 2026-07-24 14:14 UTCEPSS rescore
  40. 2026-07-24 14:14 UTCEPSS rescore
  41. 2026-07-23 14:15 UTCEPSS rescore
  42. 2026-07-23 01:38 UTCEG score recompute
  43. 2026-07-22 22:19 UTCEG score recompute▲ 0.10
  44. 2026-07-22 14:05 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:04 UTCEPSS rescore
  48. 2026-07-20 17:04 UTCEPSS rescore
  49. 2026-07-20 07:04 UTCOSV refresh
  50. 2026-07-19 14:28 UTCEPSS rescore
  51. 2026-07-19 14:28 UTCEPSS rescore
  52. 2026-07-19 02:26 UTCEPSS rescore
  53. 2026-07-19 02:26 UTCEPSS rescore
  54. 2026-07-18 10:01 UTCEPSS rescore
  55. 2026-07-16 16:59 UTCEPSS rescore
  56. 2026-07-16 16:59 UTCEPSS rescore
  57. 2026-07-15 16:55 UTCEPSS rescore
  58. 2026-07-15 16:55 UTCEPSS rescore
  59. 2026-07-13 22:27 UTCEPSS rescore
  60. 2026-07-13 06:10 UTCEPSS rescore
  61. 2026-07-13 06:10 UTCEPSS rescore
  62. 2026-07-12 05:43 UTCEPSS rescore
  63. 2026-07-12 05:43 UTCEPSS rescore
  64. 2026-07-11 08:24 UTCEPSS rescore
  65. 2026-07-11 08:24 UTCEPSS rescore
  66. 2026-07-09 19:06 UTCEPSS rescore
  67. 2026-07-08 15:11 UTCEPSS rescore
  68. 2026-07-07 13:43 UTCEPSS rescore
  69. 2026-07-06 16:25 UTCEPSS rescore
  70. 2026-07-06 16:25 UTCEPSS rescore
  71. 2026-07-06 02:20 UTCEPSS rescore
  72. 2026-07-05 02:27 UTCEPSS rescore
  73. 2026-07-04 06:28 UTCEPSS rescore
  74. 2026-07-03 00:35 UTCOSV refresh
  75. 2026-07-01 15:03 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 ↗

Related CVEs(same product + same vendor)

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 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 4.5% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-1125?
CVE-2019-1125 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2019-1125?
A fix for CVE-2019-1125 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-1125 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs