Vulnerabilities

Vulnerability · CVE-2026-0098

In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy.

Published Jun 1, 2026 · catalog updated Jul 22, 2026 · In getCallingPackageName of Shared.java,

Check if you run it

No confirmed exploitation is on record for CVE-2026-0098. EPSS is 0.07%. Act only if a listed version of In getCallingPackageName of Shared.java, is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (In getCallingPackageName of Shared.java,).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.07%
Remediation
Advisory link
Affected products
cpe google/android

In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe google/android14.0
  • cpe google/android15.0
  • cpe google/android16.0

How to fix CVE-2026-0098

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-0098. EPSS is 0.07%. Act only if a listed version of In getCallingPackageName of Shared.java, is installed.

Which versions are affected?

Compare what you have installed with 14.0, 15.0, 16.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-441. EPSS 0.07%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 1, 2026 · NIST NVD

    Detected

    In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  2. Jul 22, 2026 · NIST NVD

    Updated

    In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Sources

  • FIRST EPSSExploitation probabilityCVE-2026-0098

    30-day exploitation probability 0.1%

    first.org
  • NIST NVDVulnerability recordCVE-2026-0098

    In getCallingPackageName of Shared.java, there is a possible way to bypass activity start restrictions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.