CVE-2018-3639

HIGHNVD 5.57.4▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.4 because EPSS predicts 61% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Weaponized
7.4EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 61%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 61%CVSS: 5.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB), Variant 4.

CVSS v3
5.5
EG Score
7.4HIGHhigh confidence
EG Risk
59
EG Risk 59/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
Severity74% × 45%
Exploitation65% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
61%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

May 22, 2018

Last Modified

May 29, 2026

References (294)

Vendor Advisories for CVE-2018-3639(20)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhvm-setup-plugins-0:4.3.0-1.el7ev2019-05-08redhat
redhatqemu-kvm-rhev-10:2.9.0-16.el7_4.182019-01-23redhat
redhatlibvirt-0:0.10.2-54.el6_7.92018-10-30redhat
redhatqemu-kvm-10:1.5.3-105.el7_2.182018-10-30redhat
redhatlibvirt-0:0.10.2-18.el6_4.182018-10-30redhat
redhatkernel-alt-0:4.14.0-115.el7a2018-10-30redhat
redhatqemu-kvm-2:0.12.1.2-2.355.el6_4.122018-10-30redhat
redhatqemu-kvm-2:0.12.1.2-2.448.el6_6.72018-10-30redhat
redhatlibvirt-0:0.10.2-46.el6_6.92018-10-30redhat
redhatlibvirt-0:1.2.17-13.el7_2.92018-10-30redhat
redhatlibvirt-0:0.10.2-29.el6_5.172018-10-30redhat
redhatlibvirt-0:2.0.0-10.el7_3.132018-10-30redhat
redhatqemu-kvm-2:0.12.1.2-2.479.el6_7.82018-10-30redhat
redhatqemu-kvm-2:0.12.1.2-2.415.el6_5.192018-10-30redhat
redhatkernel-0:2.6.32-358.91.4.el62018-08-14redhat
redhatkernel-0:3.10.0-693.37.4.el72018-08-14redhat
redhatkernel-rt-1:3.10.0-693.37.4.rt56.629.el6rt2018-08-14redhat
redhatqemu-kvm-rhev-10:2.10.0-21.el7_5.42018-08-07redhat
redhatrhvm-setup-plugins-0:4.2.10-1.el7ev2018-07-31redhat
redhatkernel-0:2.6.32-504.72.1.el62018-07-31redhat
redhatkernel-0:2.6.32-573.60.1.el62018-07-24redhat
redhatrhev-hypervisor7-0:7.3-20180710.1.el7ev2018-07-24redhat
redhatkernel-0:3.10.0-327.71.1.el72018-07-17redhat
redhatkernel-0:2.6.18-433.el52018-07-11redhat
redhatkernel-0:2.6.18-348.40.1.el52018-07-11redhat
redhatkernel-0:3.10.0-514.53.1.el72018-07-10redhat

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

(37 across 26 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (96 versions)
  • every version up to 3.20180703.1: fixed in 3.20180703.1
—
linux—
  • every version up to 4.16.12-1: fixed in 4.16.12-1
—
xen—
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (96 versions)
  • every version up to 3.20180703.1: fixed in 3.20180703.1
—
linux—
  • every version up to 4.16.12-1: fixed in 4.16.12-1
—
xen—
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (96 versions)
  • every version up to 3.20180703.1: fixed in 3.20180703.1
—
linux—
  • every version up to 4.16.12-1: fixed in 4.16.12-1
—
xen—
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (96 versions)
  • every version up to 3.20180703.1: fixed in 3.20180703.1
—
linux—
  • every version up to 4.16.12-1: fixed in 4.16.12-1
—
xen—
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
—
Debian:8(3)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180703.2~bpo9+1 (99 versions)
  • every version up to 3.20180703.2~deb8u1: fixed in 3.20180703.2~deb8u1
—
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (61 versions)
  • every version up to 3.16.59-1: fixed in 3.16.59-1
  • every version up to 3.16.64-1: fixed in 3.16.64-1
—
linux-4.94.9.110-1~deb8u1
  • every version up to 4.9.110-1~deb8u1: fixed in 4.9.110-1~deb8u1
  • every version up to 4.9.144-3.1~deb8u1: fixed in 4.9.144-3.1~deb8u1
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20180807a.1~deb8u1 (105 versions)
  • every version up to 3.20180703.2~deb9u1: fixed in 3.20180703.2~deb9u1
  • every version up to 3.20180807a.1~deb9u1: fixed in 3.20180807a.1~deb9u1
—
xen4.8.1-1+deb9u1 ... 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6 (8 versions)
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.7.6-r0: fixed in 4.7.6-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.4-r0: fixed in 4.8.4-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.9.2-r3: fixed in 4.9.2-r3
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.10.1-r3: fixed in 4.10.1-r3
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.11.0-r0: fixed in 4.11.0-r0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 18× 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 131 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-44695✓ verified
    First seen May 22, 2018

    AMD / ARM / Intel - Speculative Execution Variant 4 Speculative Store Bypass

    Open source ↗
  • GitHub PoCmmxsrup/CVE-2018-3639
    First seen May 11, 2019

    Speculative Store Bypass (CVE-2018-3639) proof of concept for Linux

    Open source ↗
  • GitHub PoCtyhicks/ssbd-tools
    First seen May 31, 2018

    Tools to exercise the Linux kernel mitigation for CVE-2018-3639 (aka Variant 4) using the Speculative Store Bypass Disable (SSBD) feature of x86 processors

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-3639?
CVE-2018-3639 is a high vulnerability published on May 22, 2018. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store…
When was CVE-2018-3639 disclosed?
CVE-2018-3639 was first published on May 22, 2018, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-3639 actively exploited?
CVE-2018-3639 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 61% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-3639?
CVE-2018-3639 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4 (HIGH).
How do I remediate CVE-2018-3639?
A fix for CVE-2018-3639 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-3639 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-2018-3639

Explore →

Is Your Infrastructure Affected by CVE-2018-3639?

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

Book a Demo →Browse All CVEs