CVE-2026-49160

HIGHPre-NVD 7.58.1▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.1 because EPSS predicts 54% probability of exploitation within the next 30 days (top 1.1% of all CVEs). a secondary CVSS source baseline 7.5 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.1EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
CISA-KEV: Not listedEPSS PROB: 54%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Uncontrolled resource consumption in HTTP/2 allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
8.1(high)
EG Risk
73(Track)
EG Risk 73/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
Severity81% × 45%
Exploitation54% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
54%
EPSS %ILE
99%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-49160

Vendor Advisories for CVE-2026-49160(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 90× 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 179 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCdhmosfunk/CVE-2026-49160-CVE-2026-47291-HTTP.sys
    First seen Jun 15, 2026

    HTTP.sys Denial of Service Vulnerability & HTTP.sys Remote Code Execution Vulnerability

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-49160?
CVE-2026-49160 is a high vulnerability published on June 9, 2026. Uncontrolled resource consumption in HTTP/2 allows an unauthorized attacker to deny service over a network.
When was CVE-2026-49160 disclosed?
CVE-2026-49160 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49160 actively exploited?
CVE-2026-49160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54% probability of exploitation in the next 30 days, which ranks it in the top 1.1% of all scored CVEs.
What is the CVSS score of CVE-2026-49160?
CVE-2026-49160 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2026-49160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49160, 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-2026-49160

Explore →

Is Your Infrastructure Affected by CVE-2026-49160?

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

Start Free Scan →Browse All CVEs