Exploited in the wildMEDIUMCISA KEV

Openwave Webtop Media Transcoder file-type restriction bypass exploited, in CISA KEV

An authenticated user can make Openwave's Webtop Media Transcoder convert file types that administrators have blocked. Openwave told JVN that attacks have been observed, and CISA set a 2026-11-24 deadline. Upgrade to 1.1.22.0 or later, preferably the latest Media Server 2.0 release.

Openwave Messaging Webtop Media TranscoderCVE-2026-111793CVSS4.3CWE-669Email
Published Nov 13, 2026

JVN relays the developer's statement that attacks have been observed, and CISA added the CVE to KEV on 2026-11-10 2,3. No source gives an actor, start date or victim data.

Dec 6, 20211814 daysNov 24, 2026

What you need to know

  • Affects Openwave Webtop Media Transcoder before 1.1.22.0. The transcoder is the document-conversion component tied to Openwave's webmail product.
  • An authenticated user who bypasses the Webmail experience can get restricted file types converted. The vendor scores it CVSS 4.3, but JVN says sensitive data may be exposed.
  • Openwave told JVN that attacks have been observed (JVN note published 2026-11-09). The CVE has been in CISA KEV since 2026-11-10, with a federal due date of 2026-11-24.
  • Fix: run 1.1.22.0 or later. The vendor recommends the latest supported Media Server 2.0 release.
  • Hunt for transcoder requests that do not come from Webmail front-end hosts, and for conversions of file types outside your allowlist.

What's happening

CVE-2026-111793 is a flaw in Openwave Messaging's Webtop Media Transcoder. It lets an authenticated user have document types processed and converted even when administrators have restricted them 1,3. SecurityWeek describes the transcoder as the document-conversion component of Openwave's webmail product 4. The vendor rates the flaw CVSS 3.1 4.3 (Medium) 1; the published CVSS vector records no confidentiality or integrity impact and low availability impact. JVN goes further. It says an authenticated attacker who uploads a crafted file may be able to obtain sensitive information, and it labels the entry Critical 2. No source explains the gap between these two assessments.

All versions before 1.1.22.0 are affected 1,2. The vendor dates that fixed build to 2021-12-06 but did not publish its advisory until 2026-10-07 1. Deployments still running older builds are the ones at risk. No source gives exposure counts or says whether the component is internet-facing by default.

On 2026-11-09, JPCERT/CC and IPA published JVNVU#93403064, relaying the developer's statement that attacks exploiting the flaw have been observed 2. CISA added the CVE to its KEV catalog on 2026-11-10 with a federal due date of 2026-11-24, and lists ransomware use as unknown 3. The vendor's own advisory does not mention exploitation 1. No source names an actor, a start date, victim counts or what was accessed. SecurityWeek and The Hacker News cover this flaw alongside Cisco BroadWorks CVE-2026-20320, but neither links the two campaigns 4,5.

How it works

The vendor gives the root cause as the transcoder failing to enforce administrator-defined restrictions on which file types it converts 1. JVN and CISA classify the weakness as CWE-669, Incorrect Resource Transfer Between Spheres 2,3. In practice, a control that operators rely on to limit what the transcoder accepts is simply not applied.

Exploitation requires a valid authenticated account 1; the CVSS vector adds network access and no user interaction. The vendor says the issue arises when the Webmail experience is bypassed, which implies the transcoder is reached directly rather than through the normal webmail flow 1. The key exposure question is therefore whether any network path reaches the transcoder without passing through the Webmail front end.

The vendor limits the impact to unintended file conversion 1, and the CVSS vector scores only low availability impact. JVN alone says a specially crafted upload may yield sensitive information 2. Until the vendor clarifies, defenders should plan for the broader outcome.

What to do

In order of priority
  1. 1

    Upgrade Webtop Media Transcoder to 1.1.22.0 or later. The vendor recommends moving to the latest supported Media Server 2.0 release 1. JVN advises contacting the developer for patch details 2; do so to confirm which build fully addresses this CVE.

  2. 2

    US federal agencies must apply vendor mitigations under BOD 26-04, or stop using the product, by 2026-11-24 3.

  3. 3

    Restrict network access so the transcoder accepts requests only from the Webmail front end. This closes the bypass path the vendor describes 1.

  4. 4

    Reduce the authenticated accounts that can reach the transcoder. Disable dormant, shared and test accounts.

  5. 5

    Exploitation started on an unknown date, so treat hosts that ran affected builds as possibly compromised. Review transcoder and webmail logs for unexpected conversions and data access, and rotate credentials for any accounts tied to suspicious activity. The CISA entry does not mandate forensic triage 3.

Detection

  • Inventory Webtop Media Transcoder instances and their build numbers. Any build below 1.1.22.0 is affected 1. The vendor advisory includes no detection guidance, log signatures or IOCs 1.
  • Map which hosts can send requests to the transcoder. Requests that do not come from Webmail front-end hosts match the reported bypass precondition 1. Review firewall, load balancer and transcoder access logs for such clients.
  • Review transcoder conversion logs for file types outside the administrator-defined allowlist. Their presence shows the restriction was not enforced 1.
  • Correlate transcoder activity with authenticated webmail accounts. Flag accounts that call the transcoder without a matching webmail session, that upload unusual volumes, or that submit unusual file types.
  • JVN says sensitive information may be exposed 2. Check whether accounts that submitted unusual files then retrieved converted output, and look for repeated or large downloads after conversions.

Timeline

  1. Webtop Media Transcoder 1.1.22.0, the first fixed build, released (per the vendor). 1

  2. Openwave publishes public security advisory CAN-2026-2032674. 1

  3. CVE-2026-111793 record published. 4

  4. JVN publishes JVNVU#93403064, relaying the developer's statement that exploitation has been observed. 2

  5. CISA adds CVE-2026-111793 to the KEV catalog. 3

  6. SecurityWeek and The Hacker News report the KEV addition and JVN's exploitation note. 4

  7. CISA KEV remediation due date for federal agencies. 3

Sources

Confirmed by vendor and government. Researched and drafted by the VulnDigest briefs agent from 5 sources, then checked against them by a separate review step on Nov 13, 2026.

Exploitation rests on Openwave's statement relayed by JVN, plus the CISA KEV listing that followed it. Openwave's own advisory does not mention exploitation, and no independent telemetry has been published.

Impact conflict: the vendor (CVSS 4.3) describes unintended file conversion only. JVN says sensitive data may be exposed and labels the entry Critical. Severity here follows the vendor score.

Fix date conflict: The Hacker News says the flaw was fixed in October 2026, but the vendor dates build 1.1.22.0 to 2021-12-06. Confirm with Openwave whether 1.1.22.0 alone is enough or Media Server 2.0 is required.

The vendor advisory gives only the 4.3 score; the CVSS vector comes from the CVE record. Exploitation start is unknown, so zero-day status is not set.

KEV ransomware status, BOD reference and forensic-triage flag come from the CISA KEV feed; the live CISA page could not be loaded. News reports confirm the 2026-11-10 add date and 2026-11-24 due date.

No public proof-of-concept exploit was found for this CVE.

Spotted an error? Open an issue on sochub.io.