BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-20435High confidence

This could lead to local information disclosure, if an attacker has physical access to the device, with no additional execution privileges needed

MediaTek, Inc. · MediaTek chipset

4.6MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs MediaTek, Inc. MediaTek chipset and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-2026-9160

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In preloader, there is a possible read of device unique identifiers due to a logic error. This could lead to local information disclosure, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS10607099; Issue ID: MSV-6118.

What

In preloader, there is a possible read of device unique identifiers due to a logic error. This could lead to local information disclosure, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS10607099; Issue ID: MSV-6118.

Why

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

How

An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

In preloader, there is a possible read of device unique identifiers due to a logic error. This could lead to local information disclosure, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS10607099; Issue ID: MSV-6118.

Why

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

How

An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

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
physical access → Insufficiently Protected Credentials → obtain information outside the intended access boundary
Attack surface
Physical
Privileges required
None: unauthenticated exploitation is possible
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-522 ↗

CWE-522: Insufficiently Protected Credentials. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVPhysicalAttack vector: The attacker needs physical access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-522
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1772Google Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0974Samsung Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Samsung Android ausnutzen, um seine Privilegien zu erhöhen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, und um Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260304Security Bulletin 4 Mar 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 4 Mar 2026, published on 4 March 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0679Multiples vulnérabilités dans Google Android

rg/CVERecord?id=CVE-2026-0095 Référence CVE CVE-2026-0096 https://www.cve.org/CVERecord?id=CVE-2026-0096 Référence CVE CVE-2026-0097 https://www.cve.org/CVERecord?id=CVE-2026-0097 Référence CVE CVE-2026-0098 https://www.cve.org/CVERecord?id=CVE-2026-0098 Référence CVE CVE-2026-0099 https://www.cve.org/CVERecord?id=CVE-2026-0099 Référence CVE CVE-2026-0100 https://www.cve.org/CVERecord?id=CVE-2026-0100 Référence CVE CVE-2026-20431 https://www.cve.org/CVERecord?id=CVE-2026-20431 Référence CVE CVE-2026-20432 https://www.cve.org/CVERecord?id=CVE-2026-20432 Référence CVE CVE-2026-20433 https://www.cve.org/CVERecord?id=CVE-2026-20433 Référence CVE CVE-2026-20435 https://www.cve.org/CVERecord?id=CVE-2026-20435 Référence CVE CVE-2026-20447 https://www.cve.org/CVERecord?id=CVE-2026-20447 Référence CVE CVE-2026-20448 https://www.cve.org/CVERecord?id=CVE-2026-20448 Référence CVE CVE-2026-20449 https://www.cve.org/CVERecord?id=CVE-2026-20449 Référence CVE CVE-2026-20450 https://www.cve.org/CVERecord?id=CVE-2026-20450 Référence CVE CVE-2026-20453 https://www.cve.org/CVERecord?id=CVE-2026-20453 Référence CVE CVE-2026-20454 https://www.cve.org/CVERecord?id=CVE-2026-20454 Référence CVE CVE-2026-20455 https://www.cve.org/CVERecord?id=CVE-2026-20455 Référence CVE CVE-2026-21352 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-005986Google等の複数ベンダの製品における認証情報の不十分な保護に関する脆弱性

プリローダーにおいて、ロジックエラーが原因でデバイス固有の識別子が読み取られる可能性があります。これにより、攻撃者がデバイスに物理的にアクセスできる場合、追加の実行権限を必要とせずにローカル情報が漏洩する恐れがあります。ユーザーは悪用のために操作を行う必要がありません。パッチIDはALPS10607099で、問題IDはMSV-6118です。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6820삼성전자 제품 보안 업데이트 권고

6 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0094 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0095 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0096 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0098 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0099 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-0100 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-20435 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-20453 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-20454 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-20455 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-28573 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-28574 | 삼성 갤럭시 (Android 14, 15, 16) | SMR Jun-2026 Release 1 이전 | SMR Jun-2026 Release 1 | | CVE-2026-28577 | 삼성 갤럭시 (Android 14, 15, 16) | SMR J

Official advisory ↗
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.
Fix not verified
Affected
MediaTek chipset: MT2737, MT6739, MT6761, MT6765, MT6768, MT6781, MT6789, MT6813, MT6833, MT6853, MT6855, MT6877, MT6878, MT6879, MT6880, MT6885, MT6886, MT6890, MT6893, MT6895, MT6897, MT6983, MT6985, MT6989, MT6990, MT6993, MT8169, MT8186, MT8188, MT8370, MT8390, MT8676, MT8678, MT8696, MT8793
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 2 Mar 2026 · Last source change 30 Mar 2026, 13:05 UTC · CWE-522 · Insufficiently Protected Credentials

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-2026-9160
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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.
Free version - for non-commercial use only.CVE-2026-20435 · cve.blacktree.nl