CVE-2019-0768

MEDIUMNVD 4.35.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 5.9 because EPSS predicts 49% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 4.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 27%CVSS: 4.3Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A security feature bypass vulnerability exists when Internet Explorer VBScript execution policy does not properly restrict VBScript under specific conditions, and to allow requests that should otherwise be ignored, aka 'Internet Explorer Security Feature Bypass Vulnerability'. This CVE ID is unique from CVE-2019-0761.

CVSS v3
4.3
EG Score
5.9(high)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

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
Severity59% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
27%
EPSS %ILE
98%
KEV
Not listed

Published

April 9, 2019

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

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

All Vendor Advisories

(1)

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

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.

  • GitHub PoCruthlezs/ie11_vbscript_exploit
    First seen May 23, 2019

    Exploit Generator for CVE-2018-8174 & CVE-2019-0768 (RCE via VBScript Execution in IE11)

    Open source ↗
  • Exploit-DBEDB-46567✓ verified
    First seen Mar 19, 2019

    Microsoft Internet Explorer 11 - VBScript Execution Policy Bypass in MSHTML

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-0768?
CVE-2019-0768 is a medium vulnerability published on April 9, 2019. A security feature bypass vulnerability exists when Internet Explorer VBScript execution policy does not properly restrict VBScript under specific conditions, and to allow requests that should otherwise be ignored, aka 'Internet Explorer Security Feature Bypass Vulnerability'. This CVE ID is unique…
When was CVE-2019-0768 disclosed?
CVE-2019-0768 was first published in the National Vulnerability Database on April 9, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0768 actively exploited?
CVE-2019-0768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27% probability of exploitation in the next 30 days, which ranks it in the top 2.1% of all scored CVEs.
What is the CVSS score of CVE-2019-0768?
CVE-2019-0768 has a CVSS v3 base score of 4.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.9.
How do I remediate CVE-2019-0768?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0768, 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-0768

Explore →

Is Your Infrastructure Affected by CVE-2019-0768?

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

Start Free Scan →Browse All CVEs