CVE-2026-111183

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

EUVD-2026-107395 ↗

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.
GStreamer
CWE-122 Heap-based Buffer Overflow
ETK-2026-2345Zero's internal tracking ID, independent of the CVE number., permanent identifier
11msince last run
56mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h20m
0
+4h
+6h
+8h
+10h
+12h

description

GStreamer applications using the rtpL16depay element are affected by a heap buffer overflow during RTP payload handling. An attacker who can supply RTP data to such an application may execute code in that application's process.

mitigation

No corrected version is recorded in the supplied advisory. Prevent untrusted RTP streams from reaching rtpL16depay, and isolate applications that must process them until an update is available.

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.
–
agent run time
56m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 17:15Z
Δ 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-21 17:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2345",
  "cve_id": "CVE-2026-111183",
  "display_id": "CVE-2026-111183",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-107395",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap buffer overflow in GStreamer rtpL16depay",
  "summary": "GStreamer applications using the rtpL16depay element are affected by a heap buffer overflow during RTP payload handling. An attacker who can supply RTP data to such an application may execute code in that application's process.",
  "mitigation": "No corrected version is recorded in the supplied advisory. Prevent untrusted RTP streams from reaching rtpL16depay, and isolate applications that must process them until an update is available.",
  "vendor": "GStreamer",
  "product": "GStreamer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "5903987091bb25e4f549331032cd2e3494cf8dae"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GStreamer",
      "purl": null
    }
  ],
  "cwes": [
    122
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 56.09783026666667,
  "t0_at": "2026-10-21T17:15:23.195000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T17:15:23.195000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T17:15:23.195000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111183"
    }
  }
}

published 2026-10-21 18:39Z
last change 2026-10-21 19:35Z

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.