CVE-2026-84627 A buffer overflow was addressed with improved bounds checking.
Not scored
Published
Updated
Check this codebase for CVE-2026-84627 and fix it if it is affected.
What it is: CVE-2026-84627 is a vulnerability in Apple iOS and iPadOS, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-84627 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-84627/ (Markdown: https://insights.sbomify.com/CVE-2026-84627/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-84627?
CVE-2026-84627 is a vulnerability in Apple iOS and iPadOS, published on 26 Oct 2026.
Official description
A buffer overflow was addressed with improved bounds checking. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7.2, visionOS 27. Processing a maliciously crafted image may lead to heap corruption.
Which versions are affected by CVE-2026-84627?
How do I fix CVE-2026-84627?
No fix has been published for CVE-2026-84627 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-84627 being exploited?
There is no known exploitation of CVE-2026-84627 in the wild and no public exploit code.
Sources
Also known as GHSA-8pf5-rg67-4968.