Skip to main content

Share to Clipboard EUVDEUVD-2026-113177

| CVE-2026-107026 HIGH
Incorrect Permission Assignment for Critical Resource (CWE-732)
2026-10-29 mitre GHSA-7jxx-gvx7-f497
7.5
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Install or run app on device
  2. Exploit
    Abuse insecure clipboard component permission
  3. Impact
    Overwrite another user's clipboard content

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Permission assignment review
Exploitation Conditions

Exploitation requires local presence on the device running Share to Clipboard v1.14.1 (versionCode 32): a co-installed app or a separate Android user/profile that can reach the application's improperly protected component (CWE-732 insecure permissions). The concrete prerequisite is that the vulnerable app's component permissions allow an unauthorized party to invoke the clipboard-write functionality; the attacker does not need in-app privileges or user interaction, but does need to already be executing on the same device. Limiting factors: despite the CVSS AV:N rating this is not realistically remote/unauthenticated over a network, impact is confined to overwriting clipboard content (no read/confidentiality and no availability effect), and the target must have this specific niche app version installed.

Impact

The headline CVSS 3.1 base score of 7.5 is driven entirely by the network attack vector (AV:N) combined with no privileges and no user interaction (PR:N/UI:N) and a high integrity impact (I:H). That vector is internally inconsistent with the described mechanism: this is a CWE-732 insecure-permissions flaw in an Android application (F-Droid package com.tengu.sharetoclipboard) that lets one party overwrite 'another user's clipboard content.' Insecure Android component permissions are exploited by a co-located app or another local user on the same device, not over a network - so AV:N almost certainly overstates reachability and the realistic vector is local. No EPSS probability was supplied, the CVE is not on the CISA KEV list, and no confirmed proof-of-concept or working exploit code is indicated in the input; the only exploitation-relevant reference is a third-party advisory, not verified exploit code. The vuln.today decision label is 'this_week' rather than act_now/emergency. Net assessment: this is a high-CVSS-but-modest-real-risk issue - the inflated score comes from the questionable AV:N rating, the affected product is an obscure utility app, the impact is confined to clipboard-content integrity (C:N/A:N), and there is no evidence of active or automated exploitation. Explicit conflict to verify with the vendor/CVE source: CVSS says network vector but the insecure-permissions description implies local, on-device access.

Exploit ScenarioDerived

A malicious or unprivileged app already installed on the same Android device (or a second local profile/user) abuses the insecure component permissions of Share to Clipboard v1.14.1 to write arbitrary data into another user's clipboard without authorization - a classic clipboard-hijacking primitive, e.g. silently swapping a copied value. No public exploit code is identified at time of analysis; only a third-party advisory reference exists. Because the true vector is local, an attacker must first have code running on the target device.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Share to Clipboard 1.14.1 on Android exposes an improperly protected clipboard-write component, letting an unauthenticated local attacker-such as a co-installed app or another Android user/profile on the same device-overwrite another user's clipboard contents. The published CVSS 3.1 score is 7.5 (AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:N), but the assessed vector is AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N: exploitation requires local presence on the device, integrity impact is limited to clipboard overwrite, and there is no confidentiality or availability effect. No public exploit was identified at time of analysis.

RemediationAI

No vendor-released patch or fixed version is listed in the available references at time of analysis. The most direct mitigation is to remove or disable Share to Clipboard v1.14.1 on affected Android devices until a corrected release is available; the trade-off is loss of the app's clipboard-sharing functionality. For managed fleets, block or uninstall package com.tengu.sharetoclipboard via MDM and restrict installation of untrusted or sideloaded apps in the same Android profile, accepting reduced user flexibility and administrative overhead. Minimizing additional Android users/profiles on affected devices can reduce exposure pathways, but it does not correct the underlying permission assignment and may not stop every co-installed-app path; monitor the upstream repository and the F-Droid advisory (https://github.com/FFG0d/fdroid-android-advisories/blob/main/advisories/CVE-2026-107026.md) for a fixed version.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected software is the Android app Share to Clipboard (package com.tengu.sharetoclipboard), version 1.14.1 (versionCode 32). CWE-732 (Incorrect Permission Assignment for Critical Resource) describes the root cause: an app component that performs clipboard writes is not adequately protected by an Android permission check, so another app running in the same device context or another Android user/profile can invoke that functionality without in-app privileges or user interaction. The published CVSS vector rates the attack as network-reachable, but the assessed vector is AV:L because the attacker must already be executing on the same device; the impact is an integrity-only clipboard overwrite (I:L), with no clipboard read (C:N) and no availability effect (A:N). The supplied evidence does not identify a specific Android component type or the exact intent/interface used, and the CPE data is unpopulated.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 4.0 MEDIUM

Android insecure-permissions flaw is exploited by a local on-device actor so AV:L/PR:N/UI:N; impact is limited to clipboard content integrity (I:L), with no confidentiality or availability effect.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

2
CVE Published
Oct 29, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 29, 2026 - 00:00 cve.org
HIGH 7.5

DescriptionCVE.org

Insecure permissions in Share to Clipboard v1.14.1 (versionCode 32) allows unauthorized attackers to arbitrarily overwrite another user's clipboard content.

Executive ViewAI

Why It Matters

A high-severity integrity flaw in Share to Clipboard version 1.14.1 for Android allows co-installed applications or other users/profiles on the same device to overwrite clipboard contents. While the practical impact is contained to clipboard data and requires local presence, clipboard content frequently holds sensitive information such as passwords, financial details, and personal data, so app-integrity and privacy exposure for affected users should be on leadership's radar.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: limit app installation on managed devices to approved apps, review Android permissions to detect apps with clipboard-read/write access, advise users to avoid copying sensitive data while the app is in use, and remove or disable the app on managed devices where feasible.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Rare
obscure F-Droid Android clipboard utility, negligible production footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy