CVE-2026-111378

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

GHSA-h25h-m6m4-j5vc ↗EUVD-2026-102559 ↗

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.0.0, < 3.32.0
fixed in 3.32.0
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1745Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 23h 05msince last run
1h 43mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h28m
0
+2h
+6h
+8h
+10h
+12h

description

FreeRDP versions 3.0.0 through versions before 3.32.0 can consume unbounded memory while processing pre-authentication NLA data. A remote unauthenticated attacker who can establish a TLS connection to the service could exhaust server memory and disrupt availability.

mitigation

Upgrade FreeRDP to version 3.32.0 or later. Restrict network access to exposed FreeRDP services until the upgrade is complete.

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.
–
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.33%24th percentile
agent run time
1h 43m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

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-111378

{
  "etk_id": "ETK-2026-1745",
  "cve_id": "CVE-2026-111378",
  "display_id": "CVE-2026-111378",
  "ghsa_id": "GHSA-h25h-m6m4-j5vc",
  "euvd_id": "EUVD-2026-102559",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated memory exhaustion in FreeRDP",
  "summary": "FreeRDP versions 3.0.0 through versions before 3.32.0 can consume unbounded memory while processing pre-authentication NLA data. A remote unauthenticated attacker who can establish a TLS connection to the service could exhaust server memory and disrupt availability.",
  "mitigation": "Upgrade FreeRDP to version 3.32.0 or later. Restrict network access to exposed FreeRDP services until the upgrade is complete.",
  "vendor": "FreeRDP",
  "product": "FreeRDP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0, < 3.32.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.32.0"
      ],
      "package_name": "FreeRDP",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0033,
  "epss_percentile": 0.2444,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 103.21530803333333,
  "t0_at": "2026-10-16T01:17:46.340000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T01:17:46.340000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T01:17:46.340000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111378"
    }
  }
}

published 2026-10-16 02:01Z
last change 2026-10-21 04:45Z

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.