CVE-2018-9472 is a high severity out-of-bounds write caused by an integer overflow in the bundled libxml2 library (xmlMemStrdupLoc in xmlmemory.c). NVD scores it 8.8. Google fixes it at security patch level 2018-09-01 or later. Install the device update that reaches that level. Check apps that bundle their own copy as well.
What's affected
- Product: Android, in the bundled libxml2 library (xmlMemStrdupLoc in xmlmemory.c).
- Releases listed by the bulletin: 7.0, 7.1.1, 7.1.2, 8.0 and 8.1. The NVD product list shows only some Android releases, so treat the bulletin as the fuller list.
- Fixed in: security patch level 2018-09-01 or later, according to the Android Security Bulletin for September 2018.
- Impact in the record: remote code execution in an unprivileged process, user interaction needed.
- Severity: NVD scores it 8.8 High (vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The bulletin lists it as High, type RCE. The two ratings agree.
- Weakness classes: CWE-190 (Integer Overflow or Wraparound).
How to check if you're exposed
- On the device, open Settings and find the Android security patch level, usually under About phone. The exact path varies by manufacturer. A date earlier than 2018-09-01 means the fix is not present.
- With a USB debugging connection, run
adb shell getprop ro.build.version.security_patch. It prints the patch level as a date. You need 2018-09-01 or later. - For a fleet, export the patch level from your mobile device management console and filter for dates earlier than 2018-09-01.
- Match each device against the release list above. Devices on releases outside it are not named for this CVE, but check them against the other entries in the same bulletin.
- Apps can carry their own copy of libxml2. List the native libraries each app ships, for example from its software bill of materials, because the platform patch does not update them.
What to do now
- Identify every Android device in scope and record its current security patch level.
- Roll out the manufacturer or carrier update that reaches 2018-09-01 or later. Google publishes the fixes, but each device maker decides when its devices receive them.
- For devices that no longer receive updates, plan replacement or limit what they can reach, such as corporate mail and internal apps.
- Write the update policy down, with a maximum patch age, and report exceptions.
Why it matters
This is the second libxml2 flaw in the September 2018 bulletin that appears in this group. Like CVE-2018-9466, it concerns the system copy of the library, so apps with their own bundled libxml2 are a separate question.
An integer overflow happens when arithmetic on a size wraps around to a small number. If that number is then used to allocate memory, the buffer is smaller than the data copied into it. The result here is an out-of-bounds write. The record's KEV flag is false, so CISA does not list it as exploited. The bulletin says Google had no reports of active customer exploitation or abuse of the newly reported issues in it. That is the absence of a report in the sources read, not proof that no one has tried.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
How do I find apps that bundle libxml2?
Look at the build manifests or the software bill of materials for each app. A dependency inventory lists bundled native libraries along with their versions.
Which patch level should I look for?
The Android Security Bulletin for September 2018 places this fix at 2018-09-01. Any date at or after 2018-09-01 includes it. Some makers ship it under a different update name, so check the date.
Sources
- Android Security Bulletin for September 2018: Affected releases, severity, type and the patch level that carries the fix.
Last reviewed: 19 October 2026.