In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code
Google · Android
7.8HighCVSS 3.1
Recommended action
Within 7 days
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verified
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2025-201778
No EUVD known-exploited evidence
In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verified
01
What, why and how
In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code. 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 way to bypass the cross profile intent filter due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
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 way to bypass the cross profile intent filter due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
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 ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
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 ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.None recorded
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 → vulnerable operation → 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.
CWE not yet assigned
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:H
Common 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.
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Official EUVD recordBSI · German · WID-SEC-W-2026-3251Android Patchday September 2026: Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um beliebigen Code auszuführen, Berechtigungen zu erweitern, vertrauliche Informationen offenzulegen oder Denial-of-Service-Zustände herbeizuführen.
Official advisoryBSI · German · WID-SEC-W-2025-2711Android Patchday Dezember 2025: Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um sich erweiterte Berechtigungen zu verschaffen, einen Denial-of-Service-Zustand auszulösen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.
Official advisoryCERT-FR · French · CERTFR-2026-AVI-1158Multiples vulnérabilités dans Google Android
le correctif du 05 septembre 2026
Résumé
De multiples vulnérabilités ont été découvertes dans Google Android. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et une atteinte à la confidentialité des données.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Documentation
Bulletin de sécurité Google Android du 07 septembre 2026
https://source.android.com/docs/security/bulletin/2026/2026-09-01?hl=fr
Référence CVE CVE-2025-48564
https://www.cve.org/CVERecord?id=CVE-2025-48564
Référence CVE CVE-2025-48565
https://www.cve.org/CVERecord?id=CVE-2025-48565
Référence CVE CVE-2025-48566
https://www.cve.org/CVERecord?id=CVE-2025-48566
Référence CVE CVE-2025-48651
https://www.cve.org/CVERecord?id=CVE-2025-48651
Référence CVE CVE-2026-0001
https://www.cve.org/CVERecord?id=CVE-2026-0001
Référence CVE CVE-2026-0008
https://www.cve.org/CVERecord?id=CVE-2026-0008
Référence CVE CVE-2026-0010
https://www.cve.org/CVERecord?id=CVE-2026-0010
Référence CVE CVE-2026-0054
https://www.cve.org/CVERecord?id=CVE-2026-0054
Référence CVE CVE-2026-0065
https://www.cve.org/CVERecord?id=CVE-2026-0065
Référence CVE CVE-2026-0084
https://www.cve.org/CVERecord?id=CVE-2026-00
Official advisoryCERT-FR · French · CERTFR-2025-AVI-1056Multiples vulnérabilités dans Google Android
Official advisoryCSIRT Italia · Italian · aggiornamenti-di-sicurezza-android-16Aggiornamenti di sicurezza Android
e una nuova finestra
-
-
CVE-2026-28593 : apre una nuova finestra
-
-
CVE-2026-28590 : apre una nuova finestra
-
-
CVE-2026-28584 : apre una nuova finestra
-
-
CVE-2026-28583 : apre una nuova finestra
-
-
CVE-2026-28582 : apre una nuova finestra
-
-
CVE-2026-28581 : apre una nuova finestra
-
-
CVE-2026-28572 : apre una nuova finestra
-
-
CVE-2026-27280 : apre una nuova finestra
-
-
CVE-2026-0084 : apre una nuova finestra
-
-
CVE-2026-0065 : apre una nuova finestra
-
-
CVE-2026-0054 : apre una nuova finestra
-
-
CVE-2026-0010 : apre una nuova finestra
-
-
CVE-2026-0008 : apre una nuova finestra
-
-
CVE-2025-48566 : apre una nuova finestra
-
-
CVE-2025-48565 : apre una nuova finestra
-
-
CVE-2025-48564 : apre una nuova finestra
-
-
Riferimenti (1)
https://source.android.com/docs/security/bulletin/2026/2026-09-01
Change log
Titolo della tabella
Versione
Note
Data
1.0
Pubblicato il 09-09-2026
09/09/2026
Impatto sistemico
Alto (66.66)
Argomenti
Android
Google
Data pubblicazione
09/09/26 ore 15:01
Data Ultimo Aggiornamento
09/09/26 ore 15:01
Correlati
Alert - 07/09/26 11:13
Risolte vulnerabilità nei chipset MediaTek
Aggiornamenti di sicurezza MediaTek sanano alcune vulnerabilità, di cui 5 con gravità “alta”, nei chipset MediaTek, componenti hardware impiegati in numerosi dispositivi mobili e sistemi
Official advisoryNCSC-NL · Dutch · NCSC-2025-0379Kwetsbaarheden verholpen in Google Android en Samsung Mobile
De kwetsbaarheden zijn voornamelijk gerelateerd aan onjuiste invoervalidatie, wat kan resulteren in systeemcrashes en remote denial of service-aanvallen via kwaadaardige basisstations zonder dat gebruikersinteractie vereist is. Dit vormt een risico voor de stabiliteit en integriteit van de systemen die deze technologie gebruiken.
Google meldt informatie te hebben ontvangen dat de kwetsbaarheden met kenmerk CVE-2025-48633 en CVE-2025-48572 beperkt en gericht zijn misbruikt. Deze kwetsbaarheden bevinden zich in het Android Framework en stellen een kwaadwillende in staat zich verhoogde rechten toe te kennen en toegang te krijgen tot gevoelige gegevens. Voor zover bekend moet voor succesvol misbruik de kwaadwillende het slachtoffer misleiden een malafide app te installeren.
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.
Fix not verified
Affected
17; 16-qpr2; 16; 15; 14
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
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 not yet assigned
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-201778
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.
Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link · patch, vendor advisory to no authoritative guidance recorded.
Before
authoritative remediation link · patch, vendor advisory
Affected versionsThe structured affected or fixed version information changed.
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.
Affected versionsThe structured affected or fixed version information changed.
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.
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.
CVE-2025-48565: In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code | BlackTree
