CVE-2026-119292

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

GHSA-w9xc-63w2-7q4x ↗EUVD-2026-127359 ↗

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

description

FreeSWITCH versions before 1.11.2 process some RTP or SRTP traffic from unexpected sources before discarding it. An unauthenticated attacker that can send UDP traffic to an active media port can disrupt inbound call audio, especially for calls receiving media for relay or echo.

mitigation

Upgrade freeswitch to version 1.11.2 or later. Where feasible, restrict UDP access to RTP/SRTP media ports to expected peers.

fixed in >= 1.11.2

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
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 19:31Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-17 19:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4712",
  "cve_id": "CVE-2026-119292",
  "display_id": "CVE-2026-119292",
  "ghsa_id": "GHSA-w9xc-63w2-7q4x",
  "euvd_id": "EUVD-2026-127359",
  "status": "published",
  "anchor_state": "anchored",
  "title": "RTP source-validation denial of service in FreeSWITCH",
  "summary": "FreeSWITCH versions before 1.11.2 process some RTP or SRTP traffic from unexpected sources before discarding it. An unauthenticated attacker that can send UDP traffic to an active media port can disrupt inbound call audio, especially for calls receiving media for relay or echo.",
  "mitigation": "Upgrade freeswitch to version 1.11.2 or later. Where feasible, restrict UDP access to RTP/SRTP media ports to expected peers.",
  "vendor": "signalwire",
  "product": "freeswitch",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.11.1"
      ],
      "ecosystem": "c",
      "fixed_versions": [
        ">= 1.11.2"
      ],
      "package_name": "FreeSWITCH",
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.192793066666667,
  "t0_at": "2026-11-17T19:31:00.486000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T19:31:00.486000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T19:31:00.486000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119292"
    }
  }
}

published 2026-11-17 21:38Z
last change 2026-11-18 21:43Z

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.