dbcve.org
IpadosOperating system · Apple

CVE-2022-26710

HIGH · 8.8 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 8.6 / 12.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A use after free issue was addressed with improved memory management. This issue is fixed in iOS 15.5 and iPadOS 15.5, macOS Monterey 12.4, tvOS 15.5, watchOS 8.6. Processing maliciously crafted web content may lead to arbitrary code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability in WebKit (Apple's browser engine) allows arbitrary code execution when processing maliciously crafted web content. The vulnerability stems from improper memory management that can be exploited to achieve code execution beyond the web content's sandbox.

MitigationApply the vendor-supplied updates: iOS 15.5/iPadOS 15.5, macOS Monterey 12.4, tvOS 15.5, watchOS 8.6 or later. Organizations should deploy these patches via MDM or enterprise patch management tools.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IpadosOperating system
Affected:< 15.5
Iphone OsOperating system
Affected:< 15.5
macOSOperating system
Affected:>= 12.0.0, < 12.4
TvosOperating system
Affected:< 15.5
WatchosOperating system
Affected:< 8.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS or iPadOS version
    On the device, go to Settings > General > About to view the version number, or use MDM/enterprise inventory tools to query the installed iOS/iPadOS version
    Affected if The installed version is lower than 15.5 (for example, 15.4.x or earlier)
  2. Check macOS version
    Run 'sw_vers' in Terminal or use System Preferences > About This Mac to view the macOS version, or query via enterprise patch management tools
    Affected if The installed version is 12.0.0 through 12.3.x (Monterey versions between 12.0 and 12.4)
  3. Check tvOS version
    On Apple TV, go to Settings > General > About to view the tvOS version, or query via MDM/enterprise tools
    Affected if The installed version is lower than 15.5
  4. Check watchOS version
    Open the Watch app on a paired iPhone, go to My Watch > General > About, or query via MDM/enterprise tools
    Affected if The installed version is lower than 8.6
  5. Identify WebKit usage context
    Note that this vulnerability affects any application using the WebKit rendering engine on the affected OS versions, not just Safari. Check for installed WebKit-based browsers or applications that embed web content
    Affected if The device runs an affected OS version AND uses any WebKit-based application (browsers, in-app browsers, third-party apps embedding web content)

A device is affected if it runs any version of iOS/iPadOS below 15.5, macOS 12.0 through 12.3.x, tvOS below 15.5, or watchOS below 8.6, and uses WebKit-based applications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.6 / 12.4 / 15.5 or later
Fixed in 8.612.415.5
Interim mitigation

Apply the vendor-supplied updates: iOS 15.5/iPadOS 15.5, macOS Monterey 12.4, tvOS 15.5, watchOS 8.6 or later. Organizations should deploy these patches via MDM or enterprise patch management tools.

Recommended fix High confidence

iOS 15.5, iPadOS 15.5, macOS Monterey 12.4, tvOS 15.5, watchOS 8.6

  1. For iPhone/iPad: Open Settings > General > Software Update, then download and install iOS 15.5/iPadOS 15.5
  2. For macOS: Open System Preferences > Software Update, or go to Apple menu > System Preferences > Software Update, then download and install macOS Monterey 12.4
  3. For Apple TV: Go to Settings > System > Software Updates > Update Software, then download and install tvOS 15.5
  4. For Apple Watch: On your iPhone, open the Watch app > My Watch > General > Software Update, then download and install watchOS 8.6
  5. After upgrading, verify the version by checking Settings > General > About (iPhone/iPad), Apple menu > About This Mac (macOS), or the respective Settings on tvOS/watchOS

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26710 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data