{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-58704 in the wild since at least 16 Sep 2026.","fix":"Apply the vendor's patch. US federal agencies must fix it by 19 Sep 2026.","what":"CVE-2026-58704 is a high-severity vulnerability in Google Android, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58704 and fix it if it is affected.\n\nWhat it is: CVE-2026-58704 is a high-severity vulnerability in Google Android, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2026-58704 in the wild since at least 16 Sep 2026.\n\nAffected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58704/ (Markdown: https://insights.sbomify.com/CVE-2026-58704/index.md)","id":"CVE-2026-58704","markdown":"https://insights.sbomify.com/CVE-2026-58704/index.md","name":"CVE-2026-58704","record":{"aliases":["A-484011314","GHSA-chq2-jxgv-5vfw","PUB-A-484011314"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android cellular modem","requires_auth":"none","summary":"A logic error in the Android cellular modem allows remote attackers to escalate privileges without user interaction or additional execution rights.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google_Devices","cpe":[{"product":"android","vendor":"google"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":true,"headline":"Google Pixel Improper Authorization","id":"CVE-2026-58704","indexable":true,"kev":{"dateAdded":"2026-09-16","dueDate":"2026-09-19","knownRansomwareCampaignUse":"Unknown","product":"Pixel","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.","vendorProject":"Google","vulnerabilityName":"Google Pixel Improper Authorization Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Android","id":"CVE-2026-58710"},"packages":[],"prev":{"headline":"Race condition in Android","id":"CVE-2026-58701"},"products":["Android"],"published":"2026-09-15","related":[{"cvss_score":8.8,"headline":"Android Runtime Use-After-Free","id":"CVE-2025-48543","kev_date_added":"2025-09-04","published":"2025-09-04"},{"cvss_score":8.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2023-35674","kev_date_added":"2023-09-13","published":"2023-09-11"},{"cvss_score":8.4,"headline":"Android Framework Integer Overflow","id":"CVE-2025-48595","kev_date_added":"2026-06-02","published":"2026-06-01"},{"cvss_score":8.1,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-32896","kev_date_added":"2024-06-13","published":"2024-06-13"},{"cvss_score":7.8,"headline":"Android Framework Privilege Escalation","id":"CVE-2025-48572","kev_date_added":"2025-12-02","published":"2025-12-08"},{"cvss_score":7.8,"headline":"Android Pixel Privilege Escalation","id":"CVE-2024-29748","kev_date_added":"2024-04-04","published":"2024-04-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Google"]},"summary":"A logic error in the Android cellular modem allows remote attackers to escalate privileges without user interaction or additional execution rights.","url":"https://insights.sbomify.com/CVE-2026-58704/"}