Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.13% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-48566High confidence
In multiple locations, there is a possible permission bypass due to a confused deputy
Google · Android
7.8HighCVSS 3.1
Within 7 days
Mitigation availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Medium, lowered one band.downgradedsince 8 Sep 2026
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Google Android and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Mitigation available01
What, why and how
In multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
What
In multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Why
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
In multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Why
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-20 ↗
CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Mitigation available
- Affected
- Android: 17, 16-qpr2, 16, 15, 14
- Action
- In linea con le dichiarazioni del vendor, si raccomanda di applicare le patch seguendo le indicazioni riportate nel bollettino di sicurezza, disponibile nella sezione Riferimenti.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 8 Dec 2025 · Last source change 8 Sept 2026, 18:04 UTC · CWE-20 · Improper Input Validation
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-201777
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.CSIRT Italia ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-di-sicurezza-android-16.CNA ↗
- Before
- remediation: acn.gov.it/aggiornamenti-di-sicurezza-android-16
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CNA ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Android: 16, 15, 14, 13 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Android: 17, 16-qpr2, 16, 15, 14 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Vendor guidanceAuthoritative vendor guidance changed: removed patch: android.googlesource.com/0f3e248787d88154c8592f6e055b6b3586f4877d; removed patch: android.googlesource.com/28579dff4305f764302d85f95509671eafbf62ac; 3 further removals.CNA ↗
- Before
- patch: android.googlesource.com/0f3e248787d88154c8592f6e055b6b3586f4877d · patch: android.googlesource.com/28579dff4305f764302d85f95509671eafbf62ac · patch: android.googlesource.com/4e6cf5285d0b1725fb9141e810050cfdb3fb42fd · 2 more references
- After
- no authoritative guidance recorded
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 17; 16-qpr2; 16; 15; 14 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- 17; 16-qpr2; 16; 15; 14 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.CNA ↗
- Before
- Patch available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: android.googlesource.com/0f3e248787d88154c8592f6e055b6b3586f4877d; removed remediation: android.googlesource.com/28579dff4305f764302d85f95509671eafbf62ac.security@android.com ↗
- Before
- patch: android.googlesource.com/0f3e248787d88154c8592f6e055b6b3586f4877d · patch: android.googlesource.com/28579dff4305f764302d85f95509671eafbf62ac · patch: android.googlesource.com/4e6cf5285d0b1725fb9141e810050cfdb3fb42fd · 2 more references
- After
- patch: android.googlesource.com/0f3e248787d88154c8592f6e055b6b3586f4877d · patch: android.googlesource.com/28579dff4305f764302d85f95509671eafbf62ac · patch: android.googlesource.com/4e6cf5285d0b1725fb9141e810050cfdb3fb42fd · 2 more references
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 16; 15; 14; 13 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- 17; 16-qpr2; 16; 15; 14 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 17; 16-qpr2; 16; 15; 14 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Android: 16, 15, 14, 13 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
CVE published
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.