FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.28.0, FreeRDP server implementations with the MS-RDPECAM camera device enumerator channel enabled scan attacker-supplied DeviceName and VirtualChannelName fields for a NUL terminator in channels/rdpecam/server/camera_device_enumerator_main.c and then dereference once past the scan bound, allowing a malicious RDP client to trigger a 1- to 2-byte out-of-bounds heap read. This issue is fixed in version 3.28.0.
CVE-2026-57157
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 13, 2026
Advisory Details (6)
Auto-updated Jul 10, 2026Out-of-bounds read in the camera device enumerator server (rdpecam) via unterminated DeviceName / VirtualChannelName · Advisory · FreeRDP/FreeRDP · GitHub
https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-47fr-jw86-c3fj3.28.0
Patch available: FreeRDP/FreeRDP 3.28.0
https://github.com/FreeRDP/FreeRDP/releases/tag/3.28.0[channels,rdpecam] bound channel name read in device removed pdu
Fix merged in FreeRDP/FreeRDP PR #12945 on 2026-06-22 — awaiting tagged release
https://github.com/FreeRDP/FreeRDP/pull/12945[channels,rdpecam] fix device added notification parsing
Fix merged in FreeRDP/FreeRDP PR #12930 on 2026-06-19 — awaiting tagged release
https://github.com/FreeRDP/FreeRDP/pull/12930commit bd789a31cb79 (FreeRDP/FreeRDP)
Fix landed in FreeRDP/FreeRDP commit bd789a31cb79 — awaiting tagged release
https://github.com/FreeRDP/FreeRDP/commit/bd789a31cb794750dbe5e7c0e205981074cb681acommit 02991e7b3cc0 (FreeRDP/FreeRDP)
Fix landed in FreeRDP/FreeRDP commit 02991e7b3cc0 — awaiting tagged release
https://github.com/FreeRDP/FreeRDP/commit/02991e7b3cc0b9800b09030c0e9c80bab877d668Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | winpr3-utils (3.30.0+dfsg-0ubuntu0.26.04.1) @ resolute | 2026-08-30 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| freerdp2 | 2.10.0+dfsg1-1 ... 2.9.0+dfsg1-1~bpo11+1 (32 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| freerdp2 | 2.10.0+dfsg1-1 ... 2.11.7+dfsg1-6~deb12u1 (13 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| freerdp3 | 3.15.0+dfsg-2.1 ... 3.30.0+dfsg-1~bpo13+1 (43 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| freerdp3 | 3.15.0+dfsg-2.1 ... 3.27.1+dfsg-1 (35 versions) | 3.28.0+dfsg-1 | — |
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 17× in last 7d / 80× 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 119 total refreshes for this CVE.
- 2026-08-30 06:15 UTCEG score recompute
- 2026-08-30 06:15 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 02:38 UTCEG score recompute
- 2026-08-28 02:38 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:31 UTCEG score recompute
- 2026-08-27 02:31 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:33 UTCEG score recompute
- 2026-08-26 03:33 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:22 UTCEG score recompute
- 2026-08-24 20:22 UTCVendor advisory
- 2026-08-23 21:25 UTCEG score recompute
- 2026-08-23 21:25 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 22:27 UTCEG score recompute
- 2026-08-22 22:27 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 23:30 UTCVendor advisory
- 2026-08-21 00:28 UTCEG score recompute
- 2026-08-21 00:28 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-20 01:32 UTCEG score recompute
- 2026-08-20 01:32 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:33 UTCEG score recompute
- 2026-08-18 20:33 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:18 UTCEG score recompute
- 2026-08-17 14:18 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 15:20 UTCEG score recompute
- 2026-08-16 15:20 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 16:23 UTCEG score recompute
- 2026-08-15 16:23 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:25 UTCEG score recompute
- 2026-08-14 17:25 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 18:25 UTCVendor advisory
- 2026-08-12 19:29 UTCEG score recompute
- 2026-08-12 19:29 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 20:32 UTCEG score recompute
- 2026-08-11 20:32 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 21:35 UTCVendor advisory
- 2026-08-09 22:38 UTCEG score recompute
- 2026-08-09 22:38 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 23:42 UTCEG score recompute
- 2026-08-08 23:42 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 00:45 UTCEG score recompute
- 2026-08-08 00:45 UTCVendor advisory
- 2026-08-07 01:48 UTCEG score recompute
- 2026-08-07 01:48 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 02:52 UTCEG score recompute
- 2026-08-06 02:52 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 03:55 UTCEG score recompute
- 2026-08-05 03:55 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 04:57 UTCEG score recompute
- 2026-08-04 04:57 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 06:00 UTCVendor advisory
- 2026-08-02 06:19 UTCEG score recompute
- 2026-08-02 06:19 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 07:17 UTCEG score recompute
- 2026-08-01 07:17 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 07:20 UTCEG score recompute
- 2026-07-31 07:20 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 08:19 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 09:03 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 10:05 UTCEG score recompute
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 11:06 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:08 UTCEG score recompute
- 2026-07-26 12:08 UTCVendor advisory
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p98HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p96HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-57157?
When was CVE-2026-57157 disclosed?
Is CVE-2026-57157 actively exploited?
What is the CVSS score of CVE-2026-57157?
How do I remediate CVE-2026-57157?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57157
Is Your Infrastructure Affected by CVE-2026-57157?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.