# CVE-2026-84490: This issue was addressed through improved state management.


- **Severity:** Low 2.0 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-mjw5-jpmc-vw8c

## What is CVE-2026-84490?

CVE-2026-84490 is a low-severity vulnerability in Apple iOS and iPadOS, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-84490?


## How do I fix CVE-2026-84490?

No fix has been published for CVE-2026-84490 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84490 being exploited?

There is no known exploitation of CVE-2026-84490 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84490 and fix it if it is affected.

What it is: CVE-2026-84490 is a low-severity vulnerability in Apple iOS and iPadOS, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-84490 in the wild and no public exploit code.

Affected product: Apple iOS and iPadOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84490/ (Markdown: https://insights.sbomify.com/CVE-2026-84490/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84490
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84490
- OSV: https://osv.dev/vulnerability/CVE-2026-84490

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84490/
Summaries are generated and may contain mistakes; the official description above is the record.