CWE-926: Improper Export of Android Application Components Skip to content

Security weakness

CWE-926 Improper Export of Android Application Components

A variant-level weakness that can lead to private data exposed, data, pages or code changed and downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-926?

Improper Export of Android Application Components: The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.

Business impact

What CWE-926 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Read Application Data
  • Modify Application Data

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Unexpected State
  • DoS: Crash, Exit, or Restart
  • DoS: Instability

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • Unexpected State
  • DoS: Crash, Exit, or Restart
  • DoS: Instability

Free security check

Is CWE-926 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-926

Improper Export of Android Application Components

The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.

Weakness ID
CWE-926
Type
Variant
Status
Incomplete
Applies to
Mobile
Introduced during
Architecture and Design

Prevention

How to fix CWE-926, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Limit Content Provider permissions (read/write) as appropriate.
    • Limit Content Provider permissions (read/write) as appropriate.
  2. 02

    Build and Compilation

    • If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest.
    • If you only intend to use exported components between related apps under your control, use android:protectionLevel="signature" in the xml manifest to restrict access to applications signed by you.

Detection and evidence

How CWE-926 is found, and where it has hit

The testing methods MITRE recommends for finding it.

How it is detected

  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

How we fix it

From finding to fixed: how Codefreex closes CWE-926

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-926: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-926?

CWE-926, “Improper Export of Android Application Components”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.

How serious is CWE-926?

It can affect availability, integrity, confidentiality, with impacts such as unexpected state, dos: crash, exit, or restart, dos: instability. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-926?

If they do not need to be shared by other applications, explicitly mark components with android:exported=”false” in the application manifest. If you only intend to use exported components between related apps under your control, use android:protectionLevel=”signature” in the xml manifest to restrict access to applications signed by you.

Can Codefreex check my site for CWE-926?

Yes. A senior engineer reviews your site, store or app for CWE-926 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-926 affect?

MITRE lists it as applicable to Mobile. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-926 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.