Skip to content
eastbaycyber

CVE-2026-111793: Openwave Webtop Transcoder Bypass

CVSS · Medium
4.3
In CISA KEV
Yes
Published
Nov 17
Patch SLA & TriageVector: Local
Immediate (BOD 22-01 due 2026-11-24)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 4.3
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-17
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-10. Federal agencies must patch by 2026-11-24.

Everything CISA added on 2026-11-10

Threat Intelligence
1GitHub refs
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-111793 is an authenticated file-type restriction bypass in Openwave Webtop Media Transcoder. - CISA lists the vulnerability in its Known Exploited Vulnerabilities (KEV) catalog, confirming exploitation in the wild. - The CVSS score is 4.3, but affected versions and a fixed release have not been verified. - Identify exposed deployments, apply Openwave’s mitigation, and meet the applicable November 24, 2026, CISA deadline.

AnalystImpact · assess the risk

Are You Affected?

CVE-2026-111793 affects Openwave Messaging Limited Webtop Media Transcoder. NVD describes an access-control or policy-enforcement failure: the product does not consistently enforce administrator-defined file-type restrictions when a user reaches transcoding functionality outside the intended Webmail workflow.

Field Assessment
CVE CVE-2026-111793
Product Openwave Webtop Media Transcoder
CVSS base score 4.3, Medium
CVSS vector Not included in the retrieved NVD result
Attack vector Not confirmed from the available record
Authentication Authenticated user required
Privileges required Not separately confirmed
User interaction Not confirmed
Patch available No verified fixed release identified
CISA KEV status Yes
CISA date added 2026-11-10
CISA due date 2026-11-24

The available NVD material does not provide affected-version ranges. It identifies the product but does not establish whether every release, a particular major version, or only a narrow build range is vulnerable. Administrators should compare their deployment with Openwave’s advisory rather than treating the absence of a listed range as evidence that a system is unaffected.

The referenced vendor advisory is hosted in the Openwave security-advisories-public GitHub repository, but its Markdown contents were not reliably available in the retrieved material. Until Openwave confirms applicability for a specific build, treat deployed instances as potentially affected if they expose Webtop Media Transcoder functionality and permit authenticated users to submit conversion requests.

Analyst’s take: KEV status should drive the initial response, not the Medium CVSS score. Start by finding exposed deployments and confirming their versions, then obtain the applicable Openwave mitigation without inferring a fixed release from incomplete records.

Organizations building broader exposure inventories may also benefit from comparing attack surface management tools.

The Fix, If You’re in a Hurry

CVE-2026-111793 is listed in CISA’s Known Exploited Vulnerabilities catalog. CISA added it on November 10, 2026, with a remediation due date of November 24, 2026. That status confirms exploitation in the wild, even though the available records do not identify a public proof of concept or ransomware campaign.

No specific fixed version was verified in the retrieved NVD, CISA, or accessible vendor material. Do not invent or infer a target release. Obtain the applicable upgrade or mitigation from Openwave’s advisory, validate it in a staging environment, and record the deployed product version before and after remediation.

If the vendor cannot provide an effective mitigation, CISA’s stated direction is to discontinue use where mitigations are unavailable.

Immediate Response Checklist

  1. Identify all Openwave Webtop Media Transcoder deployments.
  2. Record product versions, exposure, authentication sources, and network locations.
  3. Determine whether direct or alternate transcoding interfaces are reachable.
  4. Review logs for unusual authenticated conversion requests.
  5. Restrict access to trusted networks and the intended Webmail workflow.
  6. Apply the Openwave-approved update or mitigation.
  7. Preserve relevant logs and investigate suspicious account activity.
  8. Document remediation before the November 24, 2026, deadline where applicable.

How This Vulnerability Works

The vulnerable behavior is an incorrect resource transfer between spheres, described by CISA as an Openwave Webtop Media Transcoder issue. Administrator-defined file-type restrictions are intended to constrain which documents can be processed. The application does not reliably apply those restrictions when an authenticated user bypasses the normal Webmail experience and reaches the transcoding workflow through another path.

The likely security boundary is the transition between the Webmail-facing workflow and the underlying transcoding resource. A request accepted by the backend may receive different validation than a request submitted through the intended interface. The available evidence does not establish the exact parameter, endpoint, file parser, or internal component responsible for the failure.

This is not documented as an unauthenticated remote-code-execution issue. The known description requires an authenticated user and concerns processing unintended document types. The supplied records do not prove arbitrary code execution, unauthenticated access, data exfiltration, or server compromise.

Defenders should still assess the consequences of unauthorized conversion, including:

  • Resource exhaustion
  • Exposure of sensitive processing paths
  • Unexpected parser behavior
  • Processing of prohibited document types
  • Policy violations
  • Abuse of compromised authenticated accounts

Technical Notes: Request-Path Model

A useful defensive model is to compare the expected and bypassed paths:

Expected:
Authenticated user
  -> Webmail interface
  -> administrator file-type validation
  -> approved transcoding request
  -> conversion result

Potentially bypassed:
Authenticated user
  -> alternate/direct WebTop transcoding resource
  -> incomplete or missing file-type validation
  -> unintended document conversion

The exact URL paths, request methods, content types, and validation fields are not available in the retrieved records. Do not deploy a detection rule based on guessed endpoint names. Capture legitimate traffic in a test environment and compare it with direct or abnormal requests before creating a production signature.

Severity, Explained

NVD assigns CVE-2026-111793 a CVSS base score of 4.3, rated Medium. The score indicates a meaningful security issue, but it should not be interpreted in isolation. The vulnerability requires authentication, and the documented impact is the processing of file types that administrators attempted to prohibit.

The complete CVSS vector was not present in the retrieved NVD result. Therefore, the exact values for attack vector, attack complexity, privileges required, user interaction, scope, confidentiality, integrity, availability, and other vector components cannot be responsibly reproduced here.

Security teams should retrieve the complete NVD record and use the official vector for internal scoring, asset prioritization, and exception documentation.

CVSS does not incorporate the operational significance of CISA KEV status. In this case, the exploitation signal is more urgent than the Medium base score alone suggests. A product exposed to untrusted networks, containing sensitive documents, or serving a large authenticated user population should receive priority over an isolated instance with tightly controlled access.

Technical Notes: Interpreting the Score

Use the verified CVSS vector from the complete NVD record or vendor advisory when importing the CVE into a vulnerability-management platform:

CVE-2026-111793
CVSS: 4.3
Vector: not available in the retrieved record
Action: obtain and validate the complete vector before calculating component-level risk

Do not fill the missing vector with a guessed string. A guessed vector can produce incorrect risk rankings and misleading audit evidence.

Is It Being Exploited?

Yes. CISA confirms in-the-wild exploitation by listing CVE-2026-111793 in the Known Exploited Vulnerabilities catalog. CISA added the entry on November 10, 2026, and assigned a remediation deadline of November 24, 2026.

Organizations subject to applicable CISA requirements should follow the relevant BOD 26-04 actions and preserve evidence for forensic triage.

A public proof of concept was not confirmed in the retrieved sources. CISA’s entry also does not identify a ransomware campaign, so ransomware association is unknown, not absent. The lack of a public PoC should not reduce urgency: KEV status indicates that exploitation has occurred, regardless of whether a reproducible exploit has been published.

The documented prerequisite is an authenticated user. Investigations should include:

  • Compromised accounts
  • Abused legitimate accounts
  • Stale credentials
  • Users with access beyond their normal business need
  • Unusual authentication sources
  • Unexpected activity outside normal working hours

Internet exposure increases risk, but an internal-only deployment is not safe if an attacker can obtain or misuse a valid account.

ResponderRunbook · act now

Technical Notes: Mitigation

Use your organization’s approved software inventory and package-management process to identify the installed release. Because the exact package name and fixed version are not confirmed, a generic command that claims to upgrade this product would be unsafe. Instead, document the installed version and retrieve the vendor-approved update through the supported Openwave distribution channel:

# Record the installed Webtop Media Transcoder version using the
# product's supported administration interface or vendor command.

# Then apply the exact Openwave-provided update or mitigation.
# Do not substitute an unverified version number.

Until the vendor fix is confirmed, reduce exposure by restricting access to the transcoding endpoint to trusted networks and the intended Webmail workflow. Disable or block direct access to alternate transcoding interfaces where operationally possible.

Enforce file-type allowlists at a reverse proxy or application gateway as a compensating control. These measures are not a replacement for the vendor fix and may not address a bypass implemented inside the application.

Detecting It in Your Environment

Start with asset discovery. Search software inventories, virtual-machine images, container or appliance records, reverse-proxy configurations, DNS records, and authentication directories for Openwave Webtop Media Transcoder.

Record each instance’s:

  • Product version
  • Network location
  • Internet exposure
  • Authentication source
  • WebTop deployment role
  • Accessible transcoding interfaces
  • Administrator-defined file-type restrictions

Then examine application and web-server logs for authenticated requests that reach transcoding functionality without a corresponding normal Webmail transaction. Look for:

  • Prohibited or unexpected document extensions
  • Repeated validation failures
  • Unusual conversion volume
  • Requests from unfamiliar source addresses
  • Activity outside a user’s normal working pattern
  • Mismatched filenames and content types
  • Direct requests to alternate transcoding resources

Preserve the original logs, authentication records, proxy headers, and converted-file metadata before rotating or cleaning them.

Technical Notes: Detection Query

The exact endpoint names and log schema are not confirmed. The following query is a starting pattern that must be adapted to local field names and validated against normal traffic:

index=webtop OR index=proxy
(
  uri_path="*transcod*" OR uri_path="*convert*"
)
(
  http_user!="-" OR user!="anonymous"
)
(
  file_extension IN ("exe","dll","js","html","svg","zip","docm","xlsm","unknown")
  OR status IN (400,403,415,422)
)
| stats count as requests,
        values(file_extension) as extensions,
        values(src_ip) as source_ips,
        values(user) as users
  by user, src_ip, uri_path
| where requests >= 5

The query is intentionally conservative because the vulnerability-specific URL and field names are unavailable. Analysts should correlate results with successful Webmail sessions, user identity, source network, request body metadata, and administrator policy.

A stronger indicator is a direct transcoding request containing a file type that the organization’s configured policy explicitly prohibits.

For network monitoring, avoid relying only on file extensions. Inspect authenticated HTTP transactions for multipart uploads or conversion requests whose declared type, filename extension, and detected content type do not agree. Where TLS inspection is authorized and appropriate, compare the request path and upload metadata with the approved Webmail workflow.

If suspicious activity is found:

  1. Disable or reset the affected account.
  2. Preserve logs and authentication evidence.
  3. Review adjacent WebTop activity.
  4. Determine whether the account was compromised before the transcoding request.
  5. Identify files submitted for conversion.
  6. Preserve uploaded files and metadata for forensic review.
  7. Avoid deleting logs or files before collection is complete.

For related incident-handling guidance, see how to respond to a data breach.

Response and Recovery

If an investigation identifies suspicious use of the transcoding workflow, treat the event as a potential account-compromise or policy-bypass incident until evidence shows otherwise.

Containment

  • Restrict access to WebTop and transcoding services.
  • Disable affected accounts or require credential resets.
  • Block direct transcoding paths where operationally possible.
  • Preserve proxy, application, authentication, and endpoint telemetry.
  • Prevent suspicious uploaded files from being automatically processed or distributed.

Eradication

  • Apply the vendor-approved fix or mitigation.
  • Remove unauthorized configuration changes.
  • Review privileged and service-account access.
  • Rotate credentials if compromise is suspected.
  • Check for persistence or lateral movement from affected accounts.

Recovery

  • Restore normal access only after validation.
  • Test administrator-defined file-type restrictions.
  • Confirm that direct and alternate request paths receive consistent validation.
  • Monitor transcoding activity more closely after remediation.
  • Record the affected versions, actions taken, and evidence retained.

References and Further Reading

The following sources provide the available public evidence for this issue:

  1. CISA Known Exploited Vulnerabilities Catalog
    CVE-2026-111793 entry
    Confirms KEV inclusion, the November 10, 2026, addition date, and the November 24, 2026, remediation deadline.

  2. Openwave security advisory repository
    CAN-2026-2032674.md
    Primary source for affected versions, fixed releases, and vendor mitigation instructions. Exact version details were not verified in the retrieved material.

  3. Openwave
    Vendor website
    Consult the vendor for supported releases, product documentation, and remediation assistance.

  4. Japan Vulnerability Notes
    JVNVU93403064
    Provides additional vulnerability information and references.

  5. NVD
    CVE-2026-111793 record
    Use the complete record to verify the CVSS vector, affected configurations, and record updates.

The retrieved evidence confirms the product, description, CVSS score, and KEV status, but does not verify affected-version ranges, a fixed version, or the complete CVSS vector. Treat deployed Webtop Media Transcoder instances as potentially affected until Openwave or another authoritative record confirms otherwise.

Prioritize internet-exposed systems, obtain the vendor mitigation, preserve evidence of suspicious activity, and follow CISA’s mitigation or discontinuation guidance where applicable.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-17

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.