On this page (8 sections)
CISA has added CVE-2026-111793, a flaw in Openwave Messaging Limited's Webtop Media Transcoder, to its Known Exploited Vulnerabilities (KEV) catalog. The entry was added on 2026-11-10; the CVE itself was published on 2026-10-16.
If you run or host Openwave Webtop or Webmail, or manage mail infrastructure for customers who do, check this now. The public record is sparse, so this article separates what the sources confirm from what is still unknown, and labels any general reasoning as such.
What happened
According to the NVD entry, Webtop Media Transcoder contains an incorrect resource transfer between spheres vulnerability that may allow an authenticated user to process and convert unintended document types if bypassing the Webmail experience. The GitHub advisory words it slightly differently: the transcoder does not enforce the file type restrictions an administrator has defined for conversion.
The CISA KEV catalog lists the product under Openwave Messaging Limited, with a due date of 2026-11-24 and a required action to apply mitigations in accordance with vendor instructions. The research we reviewed shows the rest of that text only in part, so read the full catalog entry for the complete wording. The record marks known ransomware campaign use as Unknown. The exploitation status in this article rests on the KEV listing alone.
Technical details
What the sources state: administrators can define which file types the transcoder is allowed to convert, and the transcoder does not enforce those restrictions. An authenticated user may therefore be able to convert document types that were not intended to be allowed, when bypassing the Webmail experience.
CWE-669 is a broad class in which a resource or behavior moves between trust areas without the controls that should accompany it. The CVSS vector in the GitHub advisory is network reachable, low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and low availability impact.
What is not known
- Which versions are affected and which, if any, contain a fix. The GitHub advisory lists both as unknown.
- How the flaw is being exploited, by whom, and at what scale. The sources describe no observed attacks beyond the KEV listing.
- Whether it is chained with other flaws. Nothing in the research says so.
- The vendor's exact mitigation steps. A vendor advisory is referenced at GISOpenwave on GitHub, and there is a JVN entry, but their contents were not available for this article.
Who is exposed
The sources name Openwave Webtop Media Transcoder as the affected product but do not list versions or deployment conditions, so the full scope is unknown. Because the description refers to an authenticated user, an attacker would need some valid account.
The following is our general reasoning about flaws that need a login, not a finding from the research: such accounts can come from phished or reused credentials, a malicious insider, or, on services shared by many users, any ordinary customer. Hosting providers and ISPs that offer webmail to many users may want to weigh that when prioritizing.
How to check your exposure
Start with inventory. You need to know whether the transcoder exists in your environment and how it can be reached.
- Ask your mail or platform team whether Openwave Webtop or Webtop Media Transcoder is deployed, and on which hosts.
- Check the installed product and version with your vendor's admin tooling or support portal, since the sources give no version command.
- Confirm which network segments can reach the transcoder service. If anything other than the Webmail front end can reach it, treat that as a higher-risk setup.
- Review transcoder and web server logs for conversion requests that did not come through the Webmail application, or for file types your policy is meant to block.
What to do now
- Contact Openwave Messaging Limited or your reseller and ask for the fixed version or official mitigation for CVE-2026-111793. Read the vendor advisory linked above.
- Apply the vendor's mitigation or update as soon as it is available, and record the date.
- Where possible, limit network access so only the Webmail front end can reach the Media Transcoder. This is general hardening, not a vendor instruction, so confirm it will not break your deployment.
- Follow CISA's required action for this KEV entry, and read the full catalog text for what to do if no mitigation is available.
- Review multi-factor authentication and consider password resets for accounts on the affected service, since the flaw concerns authenticated users.
- Search logs back to at least 2026-10-16 for unusual conversion activity, repeated failed logins followed by a success, or access from unexpected locations.
- If you find signs of abuse, follow a standard incident process: isolate the host, preserve logs, and rotate credentials.
Detection and monitoring afterwards
Keep watching the CISA KEV entry and the vendor advisory, since affected and fixed versions may be added. Consider alerting on conversion requests that skip Webmail, spikes in conversion jobs, and logins from new countries or devices.
Public-facing webmail portals also benefit from basic hygiene: current TLS certificates, sensible security headers and a firewall in front. You can check your certificate with the free SSL checker and your headers with the security headers checker, and Webforta Monitor can alert you to certificate, DNS and header changes on your public hosts. None of these detect or block this specific flaw. For broader guidance, see website security for small business.
Timeline
| Date | Event |
|---|---|
| 2026-10-16 | CVE-2026-111793 published by NVD and added to the GitHub Advisory Database |
| 2026-11-10 | Added to the CISA KEV catalog |
| 2026-11-24 | Due date listed in the CISA KEV entry |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
