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). the CNA's CVSS baseline 7.5 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: cna:microsoft, epss, ghsa
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

August 25, 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 6× in last 7d / 47× 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 316 total refreshes for this CVE.

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

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 August 25, 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 v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending). 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