Out-of-bounds read in Remote Desktop Client allows an unauthorized attacker to disclose information over a network.
CVE-2026-61918
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity75% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 56%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 11, 2026Security 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-61918Vendor Advisories for CVE-2026-61918(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 84× in last 7d / 121× 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 121 total refreshes for this CVE.
- 2026-08-20 08:36 UTCVendor advisory
- 2026-08-20 08:36 UTCGHSA enrichment
- 2026-08-19 21:32 UTCVendor advisory
- 2026-08-19 21:32 UTCGHSA enrichment
- 2026-08-19 21:11 UTCEG score recompute
- 2026-08-19 21:11 UTCVendor advisory
- 2026-08-19 21:11 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:49 UTCVendor advisory
- 2026-08-19 16:49 UTCGHSA enrichment
- 2026-08-19 15:26 UTCVendor advisory
- 2026-08-19 15:26 UTCGHSA enrichment
- 2026-08-19 15:12 UTCVendor advisory
- 2026-08-19 15:12 UTCGHSA enrichment
- 2026-08-19 14:29 UTCVendor advisory
- 2026-08-19 14:29 UTCGHSA enrichment
- 2026-08-19 09:46 UTCVendor advisory
- 2026-08-19 09:46 UTCGHSA enrichment
- 2026-08-18 22:42 UTCGHSA enrichment
- 2026-08-18 22:08 UTCGHSA enrichment
- 2026-08-18 17:42 UTCEG score recompute
- 2026-08-18 17:42 UTCVendor advisory
- 2026-08-18 17:42 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 13:38 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-18 13:37 UTCGHSA enrichment
- 2026-08-18 05:21 UTCGHSA enrichment
- 2026-08-17 18:12 UTCVendor advisory
- 2026-08-17 18:12 UTCGHSA enrichment
- 2026-08-17 16:15 UTCEG score recompute
- 2026-08-17 16:15 UTCVendor advisory
- 2026-08-17 16:15 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:33 UTCVendor advisory
- 2026-08-17 06:33 UTCGHSA enrichment
- 2026-08-16 19:21 UTCVendor advisory
- 2026-08-16 19:21 UTCGHSA enrichment
- 2026-08-16 18:53 UTCVendor advisory
- 2026-08-16 18:53 UTCGHSA enrichment
- 2026-08-16 18:41 UTCVendor advisory
- 2026-08-16 18:41 UTCGHSA enrichment
- 2026-08-16 17:31 UTCVendor advisory
- 2026-08-16 17:31 UTCGHSA enrichment
- 2026-08-16 16:36 UTCEG score recompute
- 2026-08-16 16:36 UTCVendor advisory
- 2026-08-16 16:36 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:13 UTCEG score recompute
- 2026-08-16 07:13 UTCVendor advisory
- 2026-08-16 07:13 UTCGHSA enrichment
- 2026-08-15 20:09 UTCVendor advisory
- 2026-08-15 20:09 UTCGHSA enrichment
- 2026-08-15 09:05 UTCEG score recompute
- 2026-08-15 09:05 UTCVendor advisory
- 2026-08-15 09:05 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:01 UTCVendor advisory
- 2026-08-14 22:01 UTCGHSA enrichment
- 2026-08-14 21:16 UTCVendor advisory
- 2026-08-14 21:16 UTCGHSA enrichment
- 2026-08-14 20:25 UTCVendor advisory
- 2026-08-14 20:25 UTCGHSA enrichment
- 2026-08-14 18:37 UTCVendor advisory
- 2026-08-14 18:37 UTCGHSA enrichment
- 2026-08-14 17:32 UTCVendor advisory
- 2026-08-14 17:32 UTCGHSA enrichment
- 2026-08-14 16:46 UTCVendor advisory
- 2026-08-14 16:46 UTCGHSA enrichment
- 2026-08-14 16:27 UTCVendor advisory
- 2026-08-14 16:27 UTCGHSA enrichment
- 2026-08-14 15:39 UTCVendor advisory
- 2026-08-14 15:39 UTCGHSA enrichment
- 2026-08-14 04:35 UTCEG score recompute
- 2026-08-14 04:35 UTCVendor advisory
- 2026-08-14 04:35 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:31 UTCVendor advisory
- 2026-08-13 17:31 UTCGHSA enrichment
- 2026-08-13 16:23 UTCVendor advisory
- 2026-08-13 16:23 UTCGHSA enrichment
- 2026-08-13 15:36 UTCEG score recompute▲ 1.00
- 2026-08-13 15:36 UTCVendor advisory
- 2026-08-13 15:36 UTCGHSA enrichment
- 2026-08-13 15:36 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-08-12 18:13 UTCVendor advisory
- 2026-08-12 18:13 UTCGHSA enrichment
- 2026-08-12 15:18 UTCEG score recompute
- 2026-08-12 15:18 UTCVendor advisory
- 2026-08-12 15:18 UTCGHSA enrichment
- 2026-08-12 14:24 UTCEG score recompute
- 2026-08-12 14:24 UTCVendor advisory
- 2026-08-12 14:24 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 13:25 UTCEG score recompute
- 2026-08-12 13:25 UTCVendor advisory
- 2026-08-12 13:25 UTCGHSA enrichment
- 2026-08-12 00:18 UTCVendor advisory
- 2026-08-12 00:18 UTCGHSA enrichment
- 2026-08-11 23:41 UTCVendor advisory
- 2026-08-11 23:41 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Frequently asked(5)
What is CVE-2026-61918?
When was CVE-2026-61918 disclosed?
Is CVE-2026-61918 actively exploited?
What is the CVSS score of CVE-2026-61918?
How do I remediate CVE-2026-61918?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61918
Is Your Infrastructure Affected by CVE-2026-61918?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.