CVE-2026-118689

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

GHSA-c237-3r77-c8g5 ↗EUVD-2026-112490 ↗

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.
OvenMediaLabs OvenMediaEngine <= 0.21.0
ETK-2026-2928Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 21msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+5h09m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

OvenMediaEngine through 0.21.0 is affected by resource-exhaustion handling in the OVT listener. An unauthenticated remote attacker can keep connections active and consume buffered memory, disrupting stream relay, if they can reach that listener.

mitigation

Restrict access to the OVT listener to trusted peers and filter or monitor anomalous OVT traffic. Apply an upstream fixed release when one is published; no fixed version is identified in the available evidence.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2928",
  "cve_id": "CVE-2026-118689",
  "display_id": "CVE-2026-118689",
  "ghsa_id": "GHSA-c237-3r77-c8g5",
  "euvd_id": "EUVD-2026-112490",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OVT listener resource exhaustion in OvenMediaEngine",
  "summary": "OvenMediaEngine through 0.21.0 is affected by resource-exhaustion handling in the OVT listener. An unauthenticated remote attacker can keep connections active and consume buffered memory, disrupting stream relay, if they can reach that listener.",
  "mitigation": "Restrict access to the OVT listener to trusted peers and filter or monitor anomalous OVT traffic. Apply an upstream fixed release when one is published; no fixed version is identified in the available evidence.",
  "vendor": "OvenMediaLabs",
  "product": "OvenMediaEngine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.21.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "OvenMediaEngine",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 52.4061804,
  "t0_at": "2026-10-28T21:11:17.232000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T21:11:17.232000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T21:11:17.232000+00:00",
      "url": "https://github.com/advisories/GHSA-c237-3r77-c8g5"
    }
  }
}

published 2026-10-29 01:28Z
last change 2026-10-29 06:33Z

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.