dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 Sep 2022.
SafariWeb browser · Apple

CVE-2022-32893

HIGH · 8.8 CVSS v3.1 Published 2022-08-24
Fix available
A fix is available. Upgrade to 2.36.7 / 12.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.6.1 and iPadOS 15.6.1, macOS Monterey 12.5.1, Safari 15.6.1. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.

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 WebKit out-of-bounds write vulnerability allowing arbitrary code execution via maliciously crafted web content. This zero-day was actively exploited before the patch release in iOS/iPadOS 15.6.1, macOS Monterey 12.5.1, and Safari 15.6.1.

MitigationApply the available security updates (iOS 15.6.1, iPadOS 15.6.1, macOS 12.5.1, Safari 15.6.1) to all affected devices immediately, as this vulnerability is being actively exploited in the wild.

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.6.1
FedoraOperating system
Affected:= 35= 36
Debian LinuxOperating system
Affected:= 10.0= 11.0
IpadosOperating system
Affected:< 15.6.1
Iphone OsOperating system
Affected:< 15.6.1
macOSOperating system
Affected:>= 12.0, < 12.5.1
WebkitgtkWeb browser
Affected:< 2.36.7
Wpe WebkitWeb browser
Affected:< 2.36.7

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 Safari version on macOS
    Open Safari > Safari menu > About Safari. The version number displays next to the Safari logo.
    Affected if Version is earlier than 15.6.1
  2. Check macOS version
    Click Apple menu > About This Mac. The version number displays below the macOS name.
    Affected if macOS version is 12.0 through 12.5.1 (Monterey)
  3. Check iOS or iPadOS version on Apple mobile devices
    Go to Settings > General > About. The version number displays next to Software Version.
    Affected if iOS or iPadOS version is earlier than 15.6.1
  4. Check WebKitGTK version on Linux
    Run: dpkg -l | grep webkit2gtk (Debian) or rpm -qa | grep webkit2gtk (Fedora)
    Affected if Version is earlier than 2.36.7
  5. Check WPE WebKit version on Linux
    Run: dpkg -l | grep wpewebkit or rpm -qa | grep wpewebkit
    Affected if Version is earlier than 2.36.7

Your environment is affected if a WebKit-based browser (Safari, WebKitGTK, WPE WebKit) is running a version lower than the fixed versions listed, or if macOS/iOS/iPadOS falls within the vulnerable version ranges.

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 2.36.7 / 12.5.1 / 15.6.1 or later
Fixed in 2.36.712.5.115.6.1
Interim mitigation

Apply the available security updates (iOS 15.6.1, iPadOS 15.6.1, macOS 12.5.1, Safari 15.6.1) to all affected devices immediately, as this vulnerability is being actively exploited in the wild.

Recommended fix High confidence

Safari 15.6.1 | iOS 15.6.1 | iPadOS 15.6.1 | macOS 12.5.1 | WebKitGTK 2.36.7 | WPE WebKit 2.36.7

  1. For macOS: Upgrade to macOS Monterey 12.5.1 or later via System Preferences > Software Update
  2. For iOS/iPadOS: Upgrade to iOS 15.6.1 or iPadOS 15.6.1 or later via Settings > General > Software Update
  3. For Safari: Upgrade to Safari 15.6.1 (included with macOS 12.5.1 update)
  4. For Linux distributions (Fedora): Update to WebKitGTK version 2.36.7 or later via system package manager: dnf update webkit2gtk
  5. For Linux distributions (Debian): Update to WebKitGTK version 2.36.7 or later via apt update && apt upgrade webkit2gtk-4.0 (or webkit2gtk-4.1)
  6. For WPE WebKit: Update to version 2.36.7 or later via system package manager
Caveat Standard minor version upgrades typically have minimal breaking changes; ensure backup before OS updates

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

Fix this in Safari Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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