CVE-2026-116783

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

GHSA-mjp3-3cq2-hxj4 ↗EUVD-2026-117759 ↗

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-129 Improper Validation of Array Index
ETK-2026-3665Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 01h 51msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+25h51m
0
+2h
+4h
+6h
+8h
+10h

description

FreeSWITCH versions before 1.11.2 contain an out-of-bounds write in mod_spandsp processing of T.38 UDPTL recovery data. A peer that can provide UDPTL traffic during an established T.38 fax session can cause memory corruption and terminate the FreeSWITCH service, interrupting active calls. Exposure applies where T.38 fax services or gateways accept such traffic.

mitigation

Upgrade FreeSWITCH to >= 1.11.2 or later.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3665",
  "cve_id": "CVE-2026-116783",
  "display_id": "CVE-2026-116783",
  "ghsa_id": "GHSA-mjp3-3cq2-hxj4",
  "euvd_id": "EUVD-2026-117759",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in FreeSWITCH T.38 processing",
  "summary": "FreeSWITCH versions before 1.11.2 contain an out-of-bounds write in mod_spandsp processing of T.38 UDPTL recovery data. A peer that can provide UDPTL traffic during an established T.38 fax session can cause memory corruption and terminate the FreeSWITCH service, interrupting active calls. Exposure applies where T.38 fax services or gateways accept such traffic.",
  "mitigation": "Upgrade FreeSWITCH to >= 1.11.2 or later.",
  "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": [
    129
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.813479033333333,
  "t0_at": "2026-11-05T19:41:44.761000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T19:41:44.761000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T19:41:44.761000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116783"
    }
  }
}

published 2026-11-05 21:00Z
last change 2026-11-07 11:55Z

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.