CVE-2026-111382

waiting for further signalsZero needs more public information before it can validate it.

GHSA-9992-vx98-33c7 ↗EUVD-2026-102563 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
FreeRDP <= 3.31.1
fixed in 3.32.0
CWE-787 Out-of-bounds Write
ETK-2026-1743Zero's internal tracking ID, independent of the CVE number., permanent identifier
5d 16h 46msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h52m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

FreeRDP versions before 3.32.0 are affected by a client-side heap out-of-bounds write while handling certain RDP graphics data. A malicious RDP server may corrupt memory and potentially execute code when a FreeRDP client connects to it and processes the affected graphics stream.

mitigation

Upgrade FreeRDP to version 3.32.0 or later. Until upgrades are complete, restrict FreeRDP connections to trusted RDP servers.

fixed in 3.32.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 01:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-16 01:17Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111382

{
  "etk_id": "ETK-2026-1743",
  "cve_id": "CVE-2026-111382",
  "display_id": "CVE-2026-111382",
  "ghsa_id": "GHSA-9992-vx98-33c7",
  "euvd_id": "EUVD-2026-102563",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap out-of-bounds write in FreeRDP graphics processing",
  "summary": "FreeRDP versions before 3.32.0 are affected by a client-side heap out-of-bounds write while handling certain RDP graphics data. A malicious RDP server may corrupt memory and potentially execute code when a FreeRDP client connects to it and processes the affected graphics stream.",
  "mitigation": "Upgrade FreeRDP to version 3.32.0 or later. Until upgrades are complete, restrict FreeRDP connections to trusted RDP servers.",
  "vendor": "FreeRDP",
  "product": "FreeRDP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.31.1"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "3.32.0"
      ],
      "package_name": "freerdp",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0029,
  "epss_percentile": 0.2062,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.068211383333333,
  "t0_at": "2026-10-16T01:17:51.334000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T01:17:51.334000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T01:17:51.334000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111382"
    }
  }
}

published 2026-10-16 01:57Z
last change 2026-10-21 18:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.