Low Authentication

CVE-2026-84490 — Improper Authentication in Apple iOS and iPadOS

This issue was addressed through improved state management. This issue is fixed in iOS 27 and iPadOS 27. An attacker with physical access to a locked device may be able to bypass Digital ID authentication when iPhone Mirroring is active.

Published Oct 19, 2026 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: apple

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.19%

ahead of 8% of scored CVEs · Oct 20, 2026

Affects

Apple

iOS and iPadOS

CVSS base

2.0

Low · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Apple iOS and iPadOS).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Apple	iOS and iPadOS	< 27	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Physical

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
2.0	CVSS 3.1	Low	0.5	1.4	134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
2.0	CVSS 3.1	Low	—	—	CISA-ADP via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-287 · Improper Authentication

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.

endpoint telemetry (EDR)authentication logs

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
CVSS changed · 2.0
Oct 20, 2026 · NIST National Vulnerability Database
Source status changed · Received → Awaiting Analysis
Oct 20, 2026 · NIST National Vulnerability Database
Record published
Oct 19, 2026
Affected products added · apple/ios and ipados
Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 19, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 19, 2026 · Alertas do Telegram
CVE published
Oct 19, 2026 · apple

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

1 on the record

support.apple.com/en-us/149034
NIST National Vulnerability Database

Elsewhere on this site

Apple
every CVE for this vendor

Authentication
same class

CWE-287
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-86976 Improper Authorization in Apple iOS and iPadOS 1d
Medium CVE-2026-86963 Improper Input Validation in Apple iOS and iPadOS 1d
Medium CVE-2026-86975 Out-of-bounds Read in Apple iOS and iPadOS 1d
Unknown CVE-2026-86977 An authorization issue was addressed with improved network restrictions. This issue is… 1d
Unknown CVE-2026-86959 An input validation issue was addressed with improved input validation. This issue is… 1d
Medium CVE-2026-86953 Out-of-bounds Write in Apple iOS and iPadOS 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-84490 is "Improper Authentication in Apple iOS and iPadOS", rated Low. It affects iOS and iPadOS (Apple); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.0 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.