dbcve.org
IpadosOperating system · Apple

CVE-2022-32926

MEDIUM · 6.7 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 9.1 / 13.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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
The issue was addressed with improved bounds checks. This issue is fixed in tvOS 16.1, iOS 15.7.1 and iPadOS 15.7.1, macOS Ventura 13, watchOS 9.1, iOS 16.1 and iPadOS 16. An app with root privileges may be able to execute arbitrary code with kernel privileges.

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

This is a local privilege escalation vulnerability in Apple's kernel where an application with root privileges can execute arbitrary code with kernel-level privileges. The vulnerability was caused by insufficient bounds checking in kernel code, allowing a root-level process to corrupt kernel memory and elevate to kernel privileges.

MitigationApply the available OS updates: tvOS 16.1, iOS 15.7.1, iPadOS 15.7.1, macOS Ventura 13, watchOS 9.1, iOS 16.1, or iPadOS 16. For enterprise environments, deploy these updates via MDM or patch management tooling.

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.7.1
Iphone OsOperating system
Affected:< 15.7.1= 16.0
macOSOperating system
Affected:< 13.0
TvosOperating system
Affected:< 16.1
WatchosOperating system
Affected:< 9.1

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 device and current OS version
    On macOS, run 'sw_vers' in Terminal. On iOS/iPadOS, go to Settings > General > About. On tvOS/watchOS, go to Settings > General > About.
    Affected if Unable to determine the exact OS version installed
  2. Check if macOS is vulnerable
    If running macOS, compare the installed version (from sw_vers) against the affected range: any version less than 13.0 (Ventura) is vulnerable.
    Affected if Installed macOS version is below 13.0
  3. Check if iOS/iPadOS is vulnerable
    If running iOS or iPadOS, compare the installed version (from Settings > General > About) against the affected ranges: any version below 15.7.1, or exactly 16.0, is vulnerable.
    Affected if Installed iOS/iPadOS version is below 15.7.1 or equals 16.0
  4. Check if tvOS is vulnerable
    If running tvOS, compare the installed version (from Settings > General > About) against the affected range: any version below 16.1 is vulnerable.
    Affected if Installed tvOS version is below 16.1
  5. Check if watchOS is vulnerable
    If running watchOS, compare the installed version (from Settings > General > About) against the affected range: any version below 9.1 is vulnerable.
    Affected if Installed watchOS version is below 9.1

If the detected OS version falls within any of the affected ranges listed (macOS < 13.0, iOS/iPadOS < 15.7.1 or = 16.0, tvOS < 16.1, or watchOS < 9.1), the device is vulnerable to this kernel privilege escalation.

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 9.1 / 13.0 / 15.7.1 or later
Fixed in 9.113.015.7.1
Interim mitigation

Apply the available OS updates: tvOS 16.1, iOS 15.7.1, iPadOS 15.7.1, macOS Ventura 13, watchOS 9.1, iOS 16.1, or iPadOS 16. For enterprise environments, deploy these updates via MDM or patch management tooling.

Recommended fix High confidence

iOS 15.7.1 or iOS 16.1+/iPadOS 15.7.1 or iPadOS 16+/macOS Ventura 13/tvOS 16.1/watchOS 9.1

  1. For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS 15.7.1 or iOS 16.1 and later, or iPadOS 15.7.1 or iPadOS 16 and later
  2. For Mac: Go to System Settings > General > Software Update and upgrade to macOS Ventura 13
  3. For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 16.1
  4. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone and upgrade to watchOS 9.1
  5. After updating, verify the new OS version in Settings > General > About
Caveat Major OS upgrades may have app compatibility implications; review app updates for iOS 16/macOS Ventura requirements before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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