CVE-2022-32826
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 · uneditedAn authorization issue was addressed with improved state management. This issue is fixed in iOS 15.6 and iPadOS 15.6, macOS Big Sur 11.6.8, watchOS 8.7, tvOS 15.6, macOS Monterey 12.5, Security Update 2022-005 Catalina. An app may be able to gain root 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 · moderate confidenceThis is a local privilege escalation vulnerability in Apple's operating systems where an authorization flaw combined with improper state management allows a malicious application to gain root privileges. The vulnerability affects multiple Apple platforms including iOS, iPadOS, macOS, watchOS, and tvOS.
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< 15.6< 15.6= 10.15.7< 10.15.7>= 11.0, < 11.6.8>= 12.0, < 12.5= 10.15.7< 15.6< 8.7CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device operating systemOn iOS/iPadOS: Settings > General > About; On macOS: Apple menu > About This Mac; On tvOS: Settings > General > About; On watchOS: Settings app on iPhone paired with watch, or Settings > General > About on watchAffected if Device runs any of iOS, iPadOS, macOS, tvOS, or watchOS - this determines which version check applies
-
Check iOS or iPadOS versionNavigate to Settings > General > About and note the version number (for example, 15.5, 15.6, 16.0)Affected if Version is earlier than 15.6 (for example, 15.5, 15.4, 15.3, etc.)
-
Check macOS versionGo to Apple menu > About This Mac; the version number appears (for example, 12.4, 11.6, 10.15.7)Affected if Version is 10.15.7 exactly, OR is earlier than 10.15.7, OR falls between 11.0 and 11.6.8 (not including 11.6.8), OR falls between 12.0 and 12.5 (not including 12.5)
-
Check tvOS or watchOS versionOn tvOS: Settings > General > About; On watchOS: On the watch go to Settings > General > About, or check via paired iPhone Watch app > General > AboutAffected if tvOS version is earlier than 15.6; watchOS version is earlier than 8.7
Your device is affected if the operating system version falls within any of the vulnerable ranges listed: iOS/iPadOS/tvOS/watchOS before 15.6/8.7, or macOS versions 10.15.7, below 10.15.7, 11.0-11.6.7, or 12.0-12.4.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.710.15.711.6.8
Apply the security updates: iOS 15.6/iPadOS 15.6, macOS Big Sur 11.6.8, macOS Monterey 12.5, Security Update 2022-005 Catalina, watchOS 8.7, and tvOS 15.6. Update via Settings > General > Software Update on iOS devices or System Preferences > Software Update on macOS.
iOS 15.6, iPadOS 15.6, macOS Big Sur 11.6.8, macOS Monterey 12.5, Security Update 2022-005 Catalina, tvOS 15.6, watchOS 8.7
- Identify the current installed version of the affected Apple operating system (iOS, iPadOS, macOS, watchOS, or tvOS)
- For iOS/iPadOS devices: Go to Settings > General > Software Update and install iOS 15.6/iPadOS 15.6 or later
- For macOS Big Sur (11.x): Install macOS Big Sur 11.6.8 or later via System Preferences > Software Update
- For macOS Monterey (12.x): Install macOS Monterey 12.5 or later via System Preferences > Software Update
- For macOS Catalina (10.15.7): Install Security Update 2022-005 Catalina via System Preferences > Software Update
- For tvOS devices: Install tvOS 15.6 or later via Settings > System > Software Update
- For Apple Watch devices: Install watchOS 8.7 or later via the Watch app on iPhone
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-32826 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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