How severe is CVE-2026-55273?

No CVSS score has been assigned to CVE-2026-55273 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-55273?

CVE-2026-55273 affects the following packages: platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android), platform/frameworks/base (Android). Ecosystems affected: Android.

How do I fix CVE-2026-55273?

Update platform/frameworks/base to 17-next:2026-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55273 is resolved across your whole dependency graph.

How do I detect CVE-2026-55273 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-55273 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-55273?

O3 pinpoints whether CVE-2026-55273 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-55273 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-55273 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-55273?

CVE-2026-55273 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-55273 published, and has it been updated?

CVE-2026-55273 was published on September 1, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

Not in CISA KEV

CVE-2026-55273

CVE-2026-55273 is a Improper Input Validation vulnerability in platform/frameworks/base. O3 Security confirms whether CVE-2026-55273 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-524767048

Published

Sep 1, 2026

Updated

Sep 8, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-55273.

Real-World Exposure

4 pkgs affected

📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Description

In AppendCommentLine of AnnotationProcessor.cpp, there is a possible supply chain risk due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`platform/frameworks/base`	≥ 17-next:0&&< 17-next:2026-09-01	17-next:2026-09-01
📦Android	`platform/frameworks/base`	≥ 16:0&&< 16:2026-09-01	16:2026-09-01
📦Android	`platform/frameworks/base`	≥ 16-qpr2:0&&< 16-qpr2:2026-09-01	16-qpr2:2026-09-01
📦Android	`platform/frameworks/base`	≥ 17:0&&< 17:2026-09-01	17:2026-09-01

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update platform/frameworks/base to 17-next:2026-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55273 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-55273 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-55273. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-55273 in your dependencies?

O3 detects CVE-2026-55273 across Android dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works