/

CVE-2026-78997

Severity:

CRITICAL RISK

(9.3)

Universal XSS (CWE-79) in UC Browser for Android App

CVE-2026-78997

Deferred

Vulnerability type

Category:

Universal Cross-Site Scripting

CWE:

CWE-79

Impact:

Arbitrary JavaScript Execution and Cross-Origin Account Compromise

Severity:

CRITICAL RISK

(9.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

UC Browser for Android contains a Universal Cross-Site Scripting vulnerability that can allow attacker-controlled JavaScript to execute in the context of arbitrary origins. The issue becomes risky when a crafted URL on a UC-owned domain reaches the browser's internal JavaScript bridge and causes code to run after navigation to a victim site.

Affected context

The vulnerability affects the Android UC Browser application, specifically the

reported package and version, when browser-internal JavaScript bridge behavior

can be combined with reflected script execution on a UC-controlled domain.

The vulnerable flow involves deferred callbacks, tab navigation, and handling

of a login dialog on the destination site. Exploitability depends on the

browser exposing these capabilities across origin boundaries.

Exploit preconditions

  • Attack surface: Android browser navigation and web content execution
  • Required access: The attacker generally needs to deliver or induce

navigation to a specially crafted URL; no privileged application access is

necessarily required

  • Trigger point: Processing of attacker-controlled script through a

UC-owned domain, followed by navigation and a relevant login-dialog event

  • Why exploitation is possible: The browser's internal JavaScript bridge

permits a deferred callback to remain effective across navigation, allowing

script execution to occur in the context of a different origin

Why this happens

The underlying bug is an origin-isolation failure in the interaction between

reflected web content and a browser-provided JavaScript bridge. A script

execution capability or deferred callback associated with one origin is not

sufficiently invalidated when the tab navigates to another origin.

This maps to CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), with the universal impact amplified by

insecure bridge lifecycle and origin-boundary handling.

Potential impact

  • Attacker-controlled JavaScript may execute in the context of a victim site
  • Session data, page content, or sensitive user information could be exposed
  • Account actions could be performed using the victim's active browser state
  • Login flows and authentication-related interactions may be manipulated
  • Other browser tabs, origins, or trusted web applications may be affected

General mitigation guidance

Mitigation generally focuses on preserving strict origin isolation and

preventing web content from retaining privileged execution capabilities after

navigation.

Common defensive patterns include:

  • Neutralizing and contextually encoding untrusted content before reflecting it
  • Restricting JavaScript bridges to explicitly trusted origins and

least-privilege operations

  • Binding callbacks and bridge capabilities to the originating document and

invalidating them on navigation

  • Avoiding privileged bridge exposure to ordinary web content where possible
  • Applying restrictive content security policies and secure authentication

flow designs

  • Separating browser-internal interfaces from user-controlled pages

How teams detect issues like this

Organizations can assess similar risks through:

  • Static analysis for reflected input reaching script or HTML contexts
  • Code review of JavaScript bridge registration, callback lifetime, and

navigation handling

  • Tests that verify bridge capabilities are revoked after origin changes
  • Dynamic testing across redirects, authentication dialogs, and tab

transitions

  • Policy enforcement requiring explicit origin allowlists for native bridges

and rejecting unrestricted interfaces

  • Automated mobile application security reviews that flag cross-origin

bridge exposure and unsafe web-content integration

Sources

SourceLink
gist.github.comgist.github.com/OmriInbar-Novee/9fd65fe08c1b1cff6a19350e44425de2
gist.github.comgist.github.com/OmriInbar-Novee/ef7a92db148b2eb1ab0aa7b99a565c4c

Frequently asked

questions

It can be triggered through web navigation and specially crafted content,

provided the victim uses an affected browser version and the vulnerable

bridge and navigation conditions are met.

Direct device access is generally not required. The attacker typically needs

to get the victim to open or visit the crafted URL, while exploitability also

depends on the browser's internal bridge behavior.

Enforce strict origin checks for every bridge operation, invalidate deferred

callbacks during navigation, and avoid exposing privileged native interfaces

to untrusted web content.

Combine contextual output encoding, origin allowlists, secure bridge design,

navigation-bound capability lifetimes, and regression tests covering

cross-origin transitions and authentication flows.

Find out what's already
exploitable in your codebase.