Automated 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 searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-926 Variant Incomplete
Improper Export of Android Application Components
This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps without enforcing proper security checks. This allows…
Definition
What is CWE-926?
This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps without enforcing proper security checks. This allows unintended or malicious applications to interact with the component, potentially leading to data theft, unauthorized actions, or application compromise.
When you export an Android component without restrictions, you create an open door for other apps on the device. For Activities, this can let malicious apps launch your screens to steal data, modify your app's state, or impersonate your UI to trick users. For Services, unauthorized apps can bind to and trigger functionality, potentially performing actions they shouldn't or corrupting your app's logic. Content Providers are especially risky, as versions of Android before 4.2 automatically export them unless you explicitly set them as private, which can lead to direct data leaks.
To prevent this, always explicitly set the `android:exported` attribute in your AndroidManifest.xml and implement strong permission checks. Use signature-level permissions for components that should only communicate with your own apps. For Content Providers, explicitly declare them as not exported if they're for internal use only, and always apply URI permissions for temporary data sharing. Never rely on default export behaviors, as they often prioritize convenience over security.
Real-world impact
Real-world CVEs caused by CWE-926
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
This application is exporting an activity and a service in its manifest.xml:
- 2
Because these components have intent filters but have not explicitly set 'android:exported=false' elsewhere in the manifest, they are automatically exported so that any other application can launch them. This may lead to unintended behavior or exploits.
- 3
This application has created a content provider to enable custom search suggestions within the application:
- 4
Because this content provider is only intended to be used within the application, it does not need to be exported. However, in Android before 4.2, it is automatically exported thus potentially allowing malicious applications to access sensitive information.
Vulnerable code example
Vulnerable XML
This application is exporting an activity and a service in its manifest.xml:
<activity android:name="com.example.vulnerableApp.mainScreen">
```
...*
<intent-filter>
```
<action android:name="com.example.vulnerableApp.OPEN_UI" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
```
...*
</activity>
<service android:name="com.example.vulnerableApp.backgroundService">
```
```
...*
<intent-filter>
```
<action android:name="com.example.vulnerableApp.START_BACKGROUND" />
</intent-filter>
```
...*
</service> Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-926
- 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.
- Build and Compilation 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.
- Build and Compilation / Architecture and Design Limit Content Provider permissions (read/write) as appropriate.
- Build and Compilation / Architecture and Design Limit Content Provider permissions (read/write) as appropriate.
Detection signals
How to detect CWE-926
Plexicus auto-detects CWE-926 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions What is CWE-926?
How serious is CWE-926?
What languages or platforms are affected by CWE-926?
How can I prevent CWE-926?
How does Plexicus detect and fix CWE-926?
Where can I learn more about CWE-926?
Frequently asked questions
What is CWE-926?
This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps without enforcing proper security checks. This allows unintended or malicious applications to interact with the component, potentially leading to data theft, unauthorized actions, or application compromise.
How serious is CWE-926?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-926?
MITRE lists the following affected platforms: Mobile.
How can I 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.
How does Plexicus detect and fix CWE-926?
Plexicus's SAST engine matches the data-flow signature for CWE-926 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-926?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/926.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-926
CWE-285 Parent
Improper Authorization
This vulnerability occurs when an application fails to properly verify whether a user has permission to access specific data or perform…
CWE-1230 Sibling
Exposure of Sensitive Information Through Metadata
This vulnerability occurs when an application protects the primary source of sensitive data but fails to secure the metadata derived from…
CWE-1256 Sibling
Improper Restriction of Software Interfaces to Hardware Features
This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not…
CWE-1297 Sibling
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
This vulnerability occurs when a semiconductor chip does not properly secure sensitive data, making it accessible to third-party…
CWE-1328 Sibling
Security Version Number Mutable to Older Versions
This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back…
CWE-552 Sibling
Files or Directories Accessible to External Parties
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
CWE-732 Sibling
Incorrect Permission Assignment for Critical Resource
This vulnerability occurs when a system grants overly permissive access to a sensitive resource, allowing unauthorized users or processes…
CWE-862 Sibling
Missing Authorization
This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain…
CWE-863 Sibling
Incorrect Authorization
This vulnerability occurs when an application checks if a user is allowed to perform an action or access data, but the check is flawed or…
Ready when you are
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.