dbcve.org
SafariWeb browser · Apple

CVE-2022-26700

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
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 memory corruption issue was addressed with improved state management. This issue is fixed in tvOS 15.5, watchOS 8.6, iOS 15.5 and iPadOS 15.5, macOS Monterey 12.4, Safari 15.5. Processing maliciously crafted web content may lead to 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 memory corruption vulnerability in WebKit allows remote code execution when processing maliciously crafted web content. The issue stems from improper state management during memory operations, potentially enabling an attacker to achieve arbitrary code execution on affected devices.

MitigationApply vendor-supplied updates: iOS 15.5+, iPadOS 15.5+, macOS Monterey 12.4+, tvOS 15.5+, watchOS 8.6+, and Safari 15.5+. For enterprise environments, deploy via MDM or notify users to update immediately.

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
SafariWeb browser
Affected:< 15.5
IpadosOperating system
Affected:< 15.5
Iphone OsOperating system
Affected:< 15.5
macOSOperating system
Affected:>= 12.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. Identify the Apple product running WebKit
    Determine if the device is running iOS, iPadOS, macOS, tvOS, watchOS, or Safari browser. On iOS/iPadOS: go to Settings > General > About. On macOS: click Apple menu > About This Mac. On tvOS/watchOS: go to Settings > General > About.
    Affected if The device runs any Apple operating system listed in the affected products
  2. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number (e.g., 15.4). Compare this against the affected range of < 15.5.
    Affected if iOS version is below 15.5 or iPadOS version is below 15.5
  3. Check the installed macOS version
    On Mac, click Apple menu > About This Mac and note the macOS version (e.g., 12.3). Compare against the affected range of >= 12.0 and < 12.4.
    Affected if macOS Monterey version is 12.0, 12.1, 12.2, or 12.3
  4. Check the Safari browser version
    Open Safari > About Safari and note the version number. Compare against the affected range of < 15.5.
    Affected if Safari version is below 15.5 on any platform
  5. Check tvOS or watchOS version
    On Apple TV: go to Settings > General > About > Version. On Apple Watch: open the Watch app on iPhone > General > About > Watch Version. Compare against affected ranges of < 15.5 for tvOS and < 8.6 for watchOS.
    Affected if tvOS version is below 15.5 or watchOS version is below 8.6

The environment is affected if any Apple device runs a version below the minimum fixed version for its product line (iOS/iPadOS/tvOS/watchOS below 15.5, macOS Monterey below 12.4, Safari below 15.5).

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 vendor-supplied updates: iOS 15.5+, iPadOS 15.5+, macOS Monterey 12.4+, tvOS 15.5+, watchOS 8.6+, and Safari 15.5+. For enterprise environments, deploy via MDM or notify users to update immediately.

Recommended fix High confidence

Upgrade to iOS 15.5, iPadOS 15.5, macOS Monterey 12.4, Safari 15.5, tvOS 15.5, or watchOS 8.6 depending on device type

  1. For iPhone and iPad devices: Go to Settings > General > Software Update and upgrade to iOS 15.5 or iPadOS 15.5
  2. For Mac computers: Go to System Preferences > Software Update and upgrade to macOS Monterey 12.4
  3. For Safari browser (standalone): Update to Safari 15.5 through macOS Software Update
  4. For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 15.5
  5. For Apple Watch: On your iPhone, open the Watch app, go to General > Software Update and upgrade to watchOS 8.6
Caveat Security update only; standard Apple OS updates typically do not introduce breaking changes

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

Fix this in Safari Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA4.0 h
28.0 hours of engineering $5,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26700 — 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-26700 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