dbcve.org
SafariWeb browser · Apple

CVE-2022-32886

HIGH · 8.8 CVSS v3.1 Published 2022-09-20
Fix available
A fix is available. Upgrade to 15.7 / 16.0 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 buffer overflow issue was addressed with improved memory handling. This issue is fixed in Safari 16, iOS 16, iOS 15.7 and iPadOS 15.7. 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 buffer overflow vulnerability in WebKit allows processing of maliciously crafted web content to trigger improved memory handling issues, potentially leading to arbitrary code execution with elevated privileges.

MitigationUpdate affected Apple products to Safari 16, iOS 16, iPadOS 15.7 or later versions to remediate the vulnerability.

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:< 16.0
FedoraOperating system
Affected:= 35= 36= 37
Debian LinuxOperating system
Affected:= 10.0= 11.0
IpadosOperating system
Affected:< 15.7
Iphone OsOperating system
Affected:< 15.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, click Safari > About Safari to view the version number
    Affected if The installed version is earlier than 16.0
  2. Check iOS version on iPhone
    Go to Settings > General > About to view the iOS version
    Affected if The installed version is earlier than 15.7
  3. Check iPadOS version on iPad
    Go to Settings > General > About to view the iPadOS version
    Affected if The installed version is earlier than 15.7
  4. Check WebKitGTK version on Fedora
    Run `rpm -qa | grep -i webkit` to list installed WebKit packages, then check the version with `rpm -q <package-name>`
    Affected if WebKitGTK or webkit2gtk is installed on Fedora 35, 36, or 37 and the package version is earlier than the fixed release for this CVE
  5. Check WebKit version on Debian
    Run `dpkg -l | grep -i webkit` to list installed WebKit packages, then check the version with `dpkg -s <package-name>`
    Affected if WebKitGTK or webkit2gtk is installed on Debian 10.0 or 11.0 and the package version is earlier than the fixed release for this CVE

A user is affected if they are running Apple Safari before version 16.0, iOS or iPadOS before version 15.7, or WebKitGTK on Fedora 35/36/37 or Debian 10/11 with an unpatched version.

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 15.7 / 16.0 or later
Fixed in 15.716.0
Interim mitigation

Update affected Apple products to Safari 16, iOS 16, iPadOS 15.7 or later versions to remediate the vulnerability.

Recommended fix High confidence

Safari 16.0+ | iOS 15.7+ or 16.0+ | iPadOS 15.7+ | Fedora: apply latest security updates | Debian: apply latest security updates

  1. For Apple devices (iOS, iPadOS): Go to Settings > General > Software Update and install iOS 16 or iOS 15.7 (iPadOS 15.7)
  2. For Apple devices (iOS, iPadOS): After update, verify in Settings > General > About that the version is 15.7 or higher (or 16.x)
  3. For macOS/Safari: Update to Safari 16.0 or later via macOS Software Update (System Preferences > Software Update)
  4. For Fedora systems: Run 'sudo dnf update webkit2gtk' or 'sudo dnf update' to apply security patches
  5. For Debian Linux: Run 'sudo apt update && sudo apt upgrade' to apply security updates from Debian security repositories
  6. After updating, restart the affected device/system to ensure the fix is fully applied
Caveat No significant breaking changes expected; this is a security patch addressing a buffer overflow

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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