CVE-2026-119293

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-127361 (ENISA EUVD)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. In 1.11.2 and earlier, rtp_common_read() in src/switch_rtp.c uses one session-wide autoadj_tally to learn RTP sources that differ from the address negotiated in SDP. An unauthenticated remote attacker who sends plaintext RTP during call setup can make packets from one or more non-advertised sources reach the threshold before the legitimate endpoint, causing FreeSWITCH to adopt the source of the threshold-crossing packet as the media peer. The attacker can then receive call audio, inject media, and deny media to the legitimate endpoint without being on the media path. FreeSWITCH 1.11.2 adds two opt-in controls, but both default to zero and the release remains affected unless both are configured before RTP session creation. This vulnerability is fixed in 1.11.2.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (4)

Auto-updated Nov 17, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

FreeSWITCH: RTP Bleed and RTP Inject through unvalidated source learning – Enable Security

https://www.enablesecurity.com/advisories/ES2026-07-freeswitch-rtp-inject-rtp-bleed
GitHub release Patch Available

FreeSWITCH v1.11.2 Release

Patch available: signalwire/freeswitch v1.11.2

https://github.com/signalwire/freeswitch/releases/tag/v1.11.2
GitHub commit Patch Available

commit a38cd8073314 (signalwire/freeswitch)

Patch available: signalwire/freeswitch v1.11.2 (contains commit a38cd8073314)

https://github.com/signalwire/freeswitch/commit/a38cd8073314f7da29b16743b8dbe52fd8505ba7
GitHub advisoryMentions a patch (unverified)

FreeSWITCH plaintext RTP source learning accepts an unvalidated source (RTP Bleed and RTP Inject) · Advisory · signalwire/freeswitch · GitHub

https://github.com/signalwire/freeswitch/security/advisories/GHSA-cw2f-3w8g-4x9q

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 19:02 UTCEchelonGraph re-scored
  2. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-11-20 21:07 UTCEchelonGraph re-scored
  4. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-19 19:14 UTCEchelonGraph re-scored
  6. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-18 21:20 UTCEchelonGraph re-scored
  8. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-17 23:28 UTCEchelonGraph re-scored
  10. 2026-11-17 22:28 UTCEchelonGraph re-scored
  11. 2026-11-17 21:03 UTCENISA EUVD ID recordedEUVD-2026-127361 · Source: ENISA EUVD
  12. 2026-11-17 20:28 UTCEchelonGraph re-scored
  13. 2026-11-17 19:44 UTCEchelonGraph re-scoredFirst assessed: 9.3 CRITICAL
  14. 2026-11-17 19:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119293?
CVE-2026-119293 is a critical-severity vulnerability; its CVE record was published on November 17, 2026. FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. In 1.11.2 and earlier, rtp_common_read() in src/switch_rtp.c uses one session-wide autoadj_tally to learn RTP…
When was the CVE record for CVE-2026-119293 published?
The CVE record for CVE-2026-119293 was published on November 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-119293 actively exploited?
CVE-2026-119293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119293?
CVE-2026-119293 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119293?
A fix for CVE-2026-119293 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-119293

Explore →

Is Your Infrastructure Affected by CVE-2026-119293?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.