CVE-2026-116790

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

GHSA-rc25-33hp-6mv2 ↗EUVD-2026-117758 ↗

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-290 Authentication Bypass by Spoofing
ETK-2026-3663Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 42msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h29m
0
+4h
+6h
+8h
+10h
+12h

description

FreeSWITCH before 1.11.2 does not verify the integrity of inbound ICE connectivity checks. A network peer that can reach an ICE-enabled call's media port can redirect or interrupt media; unencrypted calls may also be monitored or altered.

mitigation

Upgrade FreeSWITCH to version 1.11.2 or later and set ice_verify_message_integrity=true. Restrict access to ICE-enabled media ports to trusted network peers where possible.

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
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 19:40Z
Δ 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-05 19:40Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3663",
  "cve_id": "CVE-2026-116790",
  "display_id": "CVE-2026-116790",
  "ghsa_id": "GHSA-rc25-33hp-6mv2",
  "euvd_id": "EUVD-2026-117758",
  "status": "published",
  "anchor_state": "anchored",
  "title": "ICE connectivity-check authentication bypass in FreeSWITCH",
  "summary": "FreeSWITCH before 1.11.2 does not verify the integrity of inbound ICE connectivity checks. A network peer that can reach an ICE-enabled call's media port can redirect or interrupt media; unencrypted calls may also be monitored or altered.",
  "mitigation": "Upgrade FreeSWITCH to version 1.11.2 or later and set `ice_verify_message_integrity=true`. Restrict access to ICE-enabled media ports to trusted network peers where possible.",
  "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": [
    290
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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": 35.953501583333335,
  "t0_at": "2026-11-05T19:40:51.226000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T19:40:51.226000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T19:40:51.226000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116790"
    }
  }
}

published 2026-11-05 20:33Z
last change 2026-11-05 22:29Z

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.