CVE-2019-1040

MEDIUMNVD 5.36.5▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 48%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

A tampering vulnerability exists in Microsoft Windows when a man-in-the-middle attacker is able to successfully bypass the NTLM MIC (Message Integrity Check) protection. An attacker who successfully exploited this vulnerability could gain the ability to downgrade NTLM security features. To exploit this vulnerability, the attacker would need to tamper with the NTLM exchange. The attacker could then modify flags of the NTLM packet without invalidating the signature. The update addresses the vulnerability by hardening NTLM MIC protection on the server-side.

CVSS v3
5.3
EG Score
6.5(high)
EG Risk
53(Track)
EG Risk 53/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
Severity65% × 45%
Exploitation48% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
48%
EPSS %ILE
99%
KEV
Not listed

Published

June 12, 2019

Last Modified

May 20, 2025

References (2)

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

Publicly available exploits

(6 references)

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

  • GitHub PoCJonyFilc/PrintSpoofer-ReflectiveDLL
    First seen Dec 6, 2025

    The Windows Print Spooler privilege escalation vulnerability (CVE-2019-1040/CVE-2019-1019) has been implemented as a Reflective DLL for penetration testing.

    Open source ↗
  • GitHub PoCQAX-A-Team/dcpwn
    First seen Jan 1, 2021

    an impacket-dependent script exploiting CVE-2019-1040

    Open source ↗
  • GitHub PoCfox-it/cve-2019-1040-scanner
    First seen Jun 24, 2019
    Open source ↗
  • GitHub PoClazaars/UltraRealy_with_CVE-2019-1040
    First seen Jun 19, 2019

    Updated version for the tool UltraRealy with support of the CVE-2019-1040 exploit

    Open source ↗
  • GitHub PoCRidter/CVE-2019-1040-dcpwn
    First seen Jun 18, 2019

    CVE-2019-1040 with Kerberos delegation

    Open source ↗
  • GitHub PoCRidter/CVE-2019-1040
    First seen Jun 14, 2019

    CVE-2019-1040 with Exchange

    Open source ↗

Frequently asked(5)

What is CVE-2019-1040?
CVE-2019-1040 is a medium vulnerability published on June 12, 2019. A tampering vulnerability exists in Microsoft Windows when a man-in-the-middle attacker is able to successfully bypass the NTLM MIC (Message Integrity Check) protection. An attacker who successfully exploited this vulnerability could gain the ability to downgrade NTLM security features. To exploit…
When was CVE-2019-1040 disclosed?
CVE-2019-1040 was first published in the National Vulnerability Database on June 12, 2019, with the most recent update on May 20, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1040 actively exploited?
CVE-2019-1040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 48% probability of exploitation in the next 30 days, which ranks it in the top 1.2% of all scored CVEs.
What is the CVSS score of CVE-2019-1040?
CVE-2019-1040 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.5.
How do I remediate CVE-2019-1040?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-1040, 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-1040

Explore →

Is Your Infrastructure Affected by CVE-2019-1040?

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

Start Free Scan →Browse All CVEs