<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku" -->

---
title: Introducing the AndroidX Security State Libraries: A...
description: Google released stable versions of the AndroidX Security State (1.1.0) and Security State Provider (1.0.0) libraries, giving developers programmatic,...
canonical: https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Introducing the AndroidX Security State Libraries: A Unified View of Device Security | daily.dev
og:description: Google released stable versions of the AndroidX Security State (1.1.0) and Security State Provider (1.0.0) libraries, giving developers programmatic,...
og:url: https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku
og:image: https://api.daily.dev/og/posts/KnOIAjGKU.png
og:image:alt: Introducing the AndroidX Security State Libraries: A Unified View of Device Security
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introducing the AndroidX Security State Libraries: A Unified View of Device Security

**[Android Developers Blog](https://daily.dev/sources/androiddev)** · 6 min read · 0 upvotes · 0 comments

## Summary

Google released stable versions of the AndroidX Security State (1.1.0) and Security State Provider (1.0.0) libraries, giving developers programmatic, component-level visibility into a device's security posture instead of relying on a single monolithic Security Patch Level. The libraries expose three patch levels—Device SPL, Published SPL, and Available SPL—across system, system modules, and kernel components, and integrate with the OSV database and Android Security Bulletin to determine whether specific CVEs are patched. Banking, fintech, healthcare, and MDM apps can use this to gate sensitive workflows (e.g., payments, biometric access) based on real patch status, while OEMs and OTA clients can standardize how update availability is reported via IPC. Android 17 also adds a Supplemental Patches XML mechanism letting OEMs declare backported fixes without waiting for a full SPL bump.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://android-developers.googleblog.com/2026/09/introducing-androidx-security-state-libraries.html>

## Questions this post answers

### What does AndroidX Security State version 1.1.0 let my Android app check about device patch status?

It lets an app query three distinct patch levels per component: Device SPL (what's installed now), Published SPL (the latest bulletin-published level), and Available SPL (what's ready to download via IPC from update clients). It covers the system, system modules, and kernel separately, and can check specific CVEs via OSV data instead of relying on one monolithic security patch level string.

_Teams gating banking or MDM features on device patch status can follow library updates like this on daily.dev._

### How can a banking app verify specific CVEs like NFC or Bluetooth fixes are patched on an Android device before allowing tap-to-pay?

The androidx.security.state library can download device-specific vulnerability reports from the Open Source Vulnerabilities (OSV) database and programmatically check whether particular high-risk CVEs have been resolved on that device, rather than trusting only the coarse security patch level string, allowing an app to require confirmation of specific fixes before authorizing sensitive workflows.

_Developers building CVE-aware authorization logic can track Android security tooling changes on daily.dev._

### What is the Supplemental Patches XML feature introduced in Android 17?

It's a mechanism that lets OEMs declare specific security fixes they've backported above the standard security patch level, without waiting for a full monolithic SPL version bump. The Security State libraries surface this granular data to apps and services so continuous patching efforts by OEMs are credited and visible immediately rather than only at the next SPL release.

_OEM and platform engineers tracking Android patch reporting changes can follow updates like this on daily.dev._

## Similar posts on daily.dev

- [Google's Android Security State Libraries Enable Component-Level Security Verification](https://daily.dev/posts/google-s-android-security-state-libraries-enable-component-level-security-verification-cq3ueaxhd) · InfoQ · 1 upvotes · 0 comments
- [Spotlight Week: Android Safety and Security](https://daily.dev/posts/spotlight-week-android-safety-and-security-htayd8cpd) · Android Developers Blog · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#android](https://daily.dev/tags/android)

[View this post on daily.dev](https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Introducing the AndroidX Security State Libraries: A Unified View of Device Security","url":"https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku"},"datePublished":"2026-09-17T19:02:15.541Z","dateModified":"2026-09-17T19:04:49.318Z","description":"Google released stable versions of the AndroidX Security State (1.1.0) and Security State Provider (1.0.0) libraries, giving developers programmatic,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/917234084539ced984e91ca6be7f854c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/917234084539ced984e91ca6be7f854c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Android Developers Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Android Developers Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/a3d55bb1d63c48e7bd91b833eb5c2c3c","url":"https://daily.dev/sources/androiddev"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,android","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Android Developers Blog","item":"https://daily.dev/sources/androiddev"},{"@type":"ListItem","position":3,"name":"Introducing the AndroidX Security State Libraries: A Unified View of Device Security"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-the-androidx-security-state-libraries-a-unified-view-of-device-security-knoiajgku#faq","mainEntity":[{"@type":"Question","name":"What does AndroidX Security State version 1.1.0 let my Android app check about device patch status?","acceptedAnswer":{"@type":"Answer","text":"It lets an app query three distinct patch levels per component: Device SPL (what's installed now), Published SPL (the latest bulletin-published level), and Available SPL (what's ready to download via IPC from update clients). It covers the system, system modules, and kernel separately, and can check specific CVEs via OSV data instead of relying on one monolithic security patch level string. Teams gating banking or MDM features on device patch status can follow library updates like this on daily.dev."}},{"@type":"Question","name":"How can a banking app verify specific CVEs like NFC or Bluetooth fixes are patched on an Android device before allowing tap-to-pay?","acceptedAnswer":{"@type":"Answer","text":"The androidx.security.state library can download device-specific vulnerability reports from the Open Source Vulnerabilities (OSV) database and programmatically check whether particular high-risk CVEs have been resolved on that device, rather than trusting only the coarse security patch level string, allowing an app to require confirmation of specific fixes before authorizing sensitive workflows. Developers building CVE-aware authorization logic can track Android security tooling changes on daily.dev."}},{"@type":"Question","name":"What is the Supplemental Patches XML feature introduced in Android 17?","acceptedAnswer":{"@type":"Answer","text":"It's a mechanism that lets OEMs declare specific security fixes they've backported above the standard security patch level, without waiting for a full monolithic SPL version bump. The Security State libraries surface this granular data to apps and services so continuous patching efforts by OEMs are credited and visible immediately rather than only at the next SPL release. OEM and platform engineers tracking Android patch reporting changes can follow updates like this on daily.dev."}}]}
```

