CVE-2026-28573
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn AndroidManifest.xml, there is a possible persistent denial of service due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a vulnerability in AndroidManifest.xml where a missing permission check allows a local attacker to cause persistent denial of service without requiring any special privileges or user interaction. The issue stems from a component (likely an Activity, Service, BroadcastReceiver, or ContentProvider) that is exported without proper permission enforcement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.0= 16.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionOpen Settings > About Phone > Android version, or run `adb shell getprop ro.build.version.release`Affected if Version is 14.0 or 16.0 (exact match)
-
Obtain the AndroidManifest.xmlDecompile the target APK using tools like apktool, or access the source code if availableAffected if You have access to the application's AndroidManifest.xml file
-
Identify exported componentsSearch AndroidManifest.xml for elements: <activity>, <service>, <receiver>, or <provider> with android:exported="true"Affected if Any component has android:exported="true" without an android:permission attribute
-
Check for missing permission enforcementFor each exported component found, verify if android:permission attribute is present; if absent, the component lacks permission enforcementAffected if An exported component lacks the android:permission attribute entirely
-
Confirm vulnerable component typeReview the component name and purpose - vulnerable components are typically Activities, Services, BroadcastReceivers, or ContentProviders that handle sensitive operationsAffected if The exported component without permission handles operations that could be exploited for denial of service
You are affected if running Android 14.0 or 16.0 AND your application has an exported component in AndroidManifest.xml that lacks the android:permission attribute, allowing any local app to trigger the component without authorization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd or enforce the appropriate android:permission attribute on the affected component(s) in AndroidManifest.xml to ensure only authorized applications can access them. If the component should not be externally accessible, set android:exported="false".
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28573 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data