Most Android threats need something from you. You install an app, grant it permissions, tap through a warning, or open a file. GhostMap needs much less. According to research published by Bitdefender Labs on Nov. 5, 2026, a specially built app package that contains no code and asks for no permissions can push an Android phone into a crash loop. Restarting doesn't fix it. Safe mode doesn't either. In most cases the only way out is a factory reset.

Bitdefender reproduced the problem on a Google Pixel 10 running Android 17 with the Aug. 5, 2026 security patch (build CP2A.260805.005), and says it affects Android 10 and later. Google has told the researchers it will not fix it through a security update. Bitdefender says it has not seen the technique used in the wild.

Some framing before going further. Help Net Security reports that Bitdefender has no CVE for the bug, and the flaw doesn't appear in Google's November 2026 Android Security Bulletin. Nobody is known to be exploiting it, so it isn't a zero-day in the strict sense. It is a publicly disclosed weakness with no fix and no patch date.

How a banking dropper led to an OS bug

The finding started with a malware sample. Bitdefender says its investigation began on Aug. 12, 2026, when a banking-malware dropper kept crashing the emulators its analysts used to study it. A dropper is a small app whose job is to install a second, more dangerous payload. The crashes turned out to come from Android itself, in the way the operating system unpacks the app file, and not from anything the malware's code did. Bitdefender says nothing in the sample suggests its author knew the file would crash anything.

An Android app ships as an APK, which is a ZIP archive with a particular layout. Each file inside a ZIP comes with metadata, including how the file was compressed and how large it claims to be once uncompressed. Bitdefender says GhostMap comes down to how Android handles two of those fields: the compression method and the declared uncompressed length.

Help Net Security's write-up describes the core problem as two system libraries that disagree about what a valid entry looks like. One library checks an entry's declared size only when the entry is marked as "stored," meaning uncompressed. The other treats anything that isn't deflated (the standard ZIP compression) as stored and maps it at the declared size. If an entry declares some third compression method, it falls into the gap between those two rules, and the system trusts a size that doesn't match the real file.

Android then maps that entry into memory, a common technique where the OS treats part of a file as if it were already in RAM. Because it trusts the declared size, the mapping comes out larger than the file behind it. When the system tries to read the part of the mapping that has no file data, the process gets a SIGBUS, a CPU fault that kills it. Help Net Security cites an example where an APK of just 8,408 bytes was mapped across about 16 MB.

Why the phone can't recover by itself

The damage depends on which part of the package is malformed. Help Net Security reports that a bad manifest, the file that describes an app to the system, crashes the package installer. A bad resource is worse. If system_server, the process that hosts most of Android, reads it, system_server crashes. It reads the resource again when it restarts, so it crashes again. One capture cited in the coverage shows 110 of those cycles.

Because system_server is so central, the phone never gets far enough into startup to let the user remove the offending app. Bitdefender says rebooting and safe mode don't break the cycle. A factory reset is the main way out. Bitdefender says that if USB debugging had already been enabled, a computer using ADB (Android Debug Bridge, the developer interface for managing a device) could in limited conditions delete the file between crashes. Factory reset erases whatever on the phone wasn't backed up.

That's why the title of Bitdefender's post says the flaw crashes your phone "before you open the app." The trigger is the system reading the package, not the user launching anything.

"Won't Fix," then "out of scope"

According to both sources, the disclosure process went like this:

  • Aug. 20, 2026: Bitdefender reports the issue to Google through the Android & Devices Vulnerability Reward Program. The report was closed as "Won't Fix (Not Reproducible)."
  • Aug. 25, 2026: Bitdefender follows up with a working proof of concept. Google's second answer says the issue is outside the scope of a security fix and will not be addressed through a security update. Bitdefender says it was forwarded to a team for possible inclusion in a future Android version.
  • Nov. 5, 2026: Bitdefender publishes its research.

Bitdefender also notes that a weaker variant of this class of problem was tracked as CVE-2016-6724 and fixed. In its reading, Google's current published severity guidelines would treat a condition that requires a factory reset as persistent and rate it High, where the 2016 bulletin rated it Moderate. Bitdefender's point is that the same area of code still has a gap that a better-built file can get through.

Google's position, as Bitdefender relays it, is that the issue falls outside the scope of a security update fix. Defenders may see it differently. Bitdefender calls the risk significant, and a free, permissionless package that can make a phone unusable until the owner erases it looks a lot like a denial-of-service weapon. Bitdefender notes that the bug crashes processes; it doesn't execute code, read data, or grant permissions.

What the November bulletin does and doesn't cover

The Android Security Bulletin for November 2026 was published Nov. 2 and updated Nov. 6. Devices on security patch level 2026-11-05 or later address the issues it lists. The most severe of those is a critical remote code execution flaw that needs no additional execution privileges. That alone makes the November update worth installing.

The bulletin doesn't mention GhostMap. A search of the page text for "GhostMap" and for "libziparchive," one of the ZIP-handling libraries involved, found nothing. Since Google has said no security update is planned, a phone fully up to date on November patches should be assumed to remain exposed to this flaw.

What It Means for Defenders

Who is affected: Per Bitdefender, devices running Android 10 and later; a Bitdefender analyst told Help Net Security the bug is in AOSP and that it did not test other manufacturers' phones. Testing was done on a Pixel 10 with Android 17 and the Aug. 5, 2026 patch. Neither source gives a fixed version, and Google has said no security update is planned. Bitdefender has not seen it exploited.

Patch anyway, for other reasons. Check that managed Android devices report security patch level 2026-11-05 or later. That covers the issues in the November bulletin. Just don't mark GhostMap as fixed because a device is current.

Plan for the reset scenario. The practical risk is a phone that gets wiped. For fleets, that means confirming device data and settings are backed up, or synced to a management console, so a factory reset costs hours and not data. Help desks should know the symptom: a device stuck rebooting that safe mode doesn't help. The cause may be a bad package, not hardware failure.

About ADB. Bitdefender says USB debugging enabled beforehand can sometimes allow recovery without a factory reset, but only under limited conditions, and not after a full kernel reboot. Don't treat that as a reason to turn ADB on across a fleet. It's a powerful interface, and most organizations keep it off on production devices for good reason.

Control what gets installed. The trigger is a crafted APK, and the original sample was a banking dropper. Limiting installs to vetted sources, blocking sideloading on managed devices, and keeping users from installing apps passed along through messages or downloads all shrink the exposure. These are standard controls. GhostMap is one more reason to enforce them. Bitdefender says its own mobile security product detects the malformation, and other security tools may offer similar protection.

For CMMC and federal contractor environments: If phones are part of your covered asset inventory, consider recording this as a known, vendor-unremediated weakness in your risk register, and note the compensating controls you rely on, such as install restrictions and backups. When an assessor asks why a "current" device is still exposed, Google's position as reported by Bitdefender is the explanation.

Watch for changes. Google has reportedly forwarded the issue to a team for possible inclusion in a future Android release. Watch for an Android version update or a later bulletin that addresses ZIP entry handling, and for any reports that the technique has turned up in real malware.

Sources