CVE-2022-26714
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 · uneditedA memory corruption issue was addressed with improved validation. This issue is fixed in tvOS 15.5, iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.4. An application 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 confidenceA memory corruption vulnerability in the Apple kernel allowed a malicious application to achieve arbitrary code execution with kernel-level privileges. The fix involved improved memory validation to prevent the corruption. The vulnerability affected multiple Apple operating systems including iOS, iPadOS, tvOS, watchOS, and macOS.
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.5< 15.5< 10.15.7= 10.15.7>= 11.0, < 11.6.6>= 12.0, < 12.4< 8.6CVSS 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 the installed Apple operating systemOn iOS/iPadOS: go to Settings > General > About. On macOS: open System Preferences > About or run 'sw_vers' in Terminal. On watchOS: open the Watch app on iPhone > General > About.Affected if The system is running any of iOS, iPadOS, macOS, or watchOS (the affected product families)
-
Check iOS or iPadOS versionOn the device, go to Settings > General > About and note the version number (e.g., 15.4, 15.5, 15.6). Compare against the affected range: any version less than 15.5 is vulnerable.Affected if The iOS or iPadOS version is below 15.5 (e.g., 15.4, 15.3, etc.)
-
Check macOS versionOpen System Preferences > About or run 'sw_vers' in Terminal. Note the major version number (e.g., 10.15.x, 11.x, 12.x). Compare against: 10.15.7 (all builds), 11.0-11.6.5, or 12.0-12.3.Affected if The macOS version is 10.15.7 (any build), 11.0 through 11.6.5, or 12.0 through 12.3
-
Check watchOS versionOn the paired iPhone, open the Watch app, go to General > About, and note the version. Alternatively, on Apple Watch go to Settings > General > About. Compare against the affected range: any version below 8.6.Affected if The watchOS version is below 8.6 (e.g., 8.5, 8.4, 8.0, etc.)
The system is affected if it is running any unpatched version of iOS, iPadOS, macOS, or watchOS that falls within the vulnerable version ranges specified for this CVE.
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.610.15.711.6.6
Apply the available security updates for the respective Apple operating systems: iOS 15.5, iPadOS 15.5, tvOS 15.5, watchOS 8.6, macOS Big Sur 11.6.6, macOS Monterey 12.4, or Security Update 2022-004 for macOS Catalina.
iOS/iPadOS 15.5, macOS Big Sur 11.6.6, macOS Monterey 12.4, macOS Catalina Security Update 2022-004, watchOS 8.6, tvOS 15.5
- Check current device/OS version in Settings > General > About (iOS/iPadOS) or System Preferences > About (macOS)
- Back up important data before updating
- For iOS/iPadOS: Go to Settings > General > Software Update and install iOS/iPadOS 15.5
- For macOS: Go to System Preferences > Software Update and install the available security update (macOS 11.6.6 for Big Sur, macOS 12.4 for Monterey, or Security Update 2022-004 for Catalina)
- For watchOS: Open the Watch app on iPhone, go to General > Software Update and install watchOS 8.6
- For tvOS: Go to Settings > System > Software Updates and install tvOS 15.5
- Restart the device after the update completes
- Verify the update was successful by checking the OS version in Settings/About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26714 — 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-26714 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