dbcve.org
IpadosOperating system · Apple

CVE-2022-26736

HIGH · 7.8 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 12.4 / 15.5 or later.
See remediation →
81/100
Remediation priority · High
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 tvOS 15.5, macOS Monterey 12.4, iOS 15.5 and iPadOS 15.5. 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 confidence

A kernel-level out-of-bounds write vulnerability in multiple Apple operating systems (iOS, iPadOS, tvOS, macOS) allows a malicious application to execute arbitrary code with kernel privileges due to insufficient bounds checking.

MitigationApply the vendor-supplied updates: iOS 15.5, iPadOS 15.5, tvOS 15.5, macOS Monterey 12.4 or later.

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.5
Iphone OsOperating system
Affected:< 15.5
macOSOperating system
Affected:>= 12.0, < 12.4
TvosOperating system
Affected:< 15.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Apple operating system
    Determine whether the device runs iOS, iPadOS, macOS, or tvOS. On iOS/iPadOS check Settings > General > About. On macOS check Apple menu > About This Mac. On tvOS check Settings > General > About.
    Affected if The device runs any of iOS, iPadOS, macOS, or tvOS.
  2. Check iOS or iPadOS version
    Go to Settings > General > About and note the Version number. Compare it to 15.5.
    Affected if The version is lower than 15.5 (for example, 15.4.1, 15.4, 15.3, etc.).
  3. Check macOS Monterey version
    Go to Apple menu > About This Mac and note the version number (for example, 12.3.1, 12.3, 12.2). Compare it to the range 12.0 to 12.4.
    Affected if The version is 12.0, 12.1, 12.2, 12.3, or 12.3.1 (any version >= 12.0 but < 12.4). Versions below 12.0 or 12.4 and later are not affected.
  4. Check tvOS version
    Go to Settings > General > About and note the Version number. Compare it to 15.5.
    Affected if The version is lower than 15.5 (for example, 15.4, 15.3, etc.).

You are affected if the device runs iOS or iPadOS below 15.5, tvOS below 15.5, or macOS Monterey version 12.0 through 12.3.1.

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 12.4 / 15.5 or later
Fixed in 12.415.5
Interim mitigation

Apply the vendor-supplied updates: iOS 15.5, iPadOS 15.5, tvOS 15.5, macOS Monterey 12.4 or later.

Recommended fix High confidence

iOS 15.5 / iPadOS 15.5 / macOS Monterey 12.4 / tvOS 15.5 (depending on device type)

  1. Identify the affected Apple device (iPhone, iPad, Mac, or Apple TV)
  2. Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Preferences > About on macOS, Settings > General > About on tvOS)
  3. Back up the device data before upgrading
  4. Upgrade iPhone or iPad to iOS 15.5 or iPadOS 15.5 via Settings > General > Software Update
  5. Upgrade Mac to macOS Monterey 12.4 via System Preferences > Software Update
  6. Upgrade Apple TV to tvOS 15.5 via Settings > General > Software Update
Caveat Minor point release; standard upgrade risks apply (review release notes for known issues)

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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