macOSOperating system · Apple

CVE-2022-26718

HIGH · 7.8 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 11.6.6 / 12.4 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 read issue was addressed with improved input validation. This issue is fixed in macOS Monterey 12.4, macOS Big Sur 11.6.6. An application may be able to gain elevated 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 confidence

A memory safety vulnerability in macOS where insufficient input validation allows an out-of-bounds read operation, which can be exploited by a malicious application to escalate privileges and gain elevated access on the affected system.

MitigationUpdate macOS devices to Monterey 12.4 or later, or Big Sur 11.6.6 or later, to incorporate the fixed input validation logic that addresses this out-of-bounds read 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
macOSOperating system
Affected:>= 11.0, < 11.6.6>= 12.0.0, < 12.4

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 macOS version
    Click Apple menu > About This Mac to display the macOS version number
    Affected if Version displays as 11.0 to 11.6.5 (Big Sur) or 12.0.0 to 12.3 (Monterey)
  2. Confirm build version (optional)
    In About This Mac, click Version number to reveal the build number (e.g., 20G90)
    Affected if Build number falls within vulnerable builds for your macOS version
  3. Check system is exposed to untrusted applications
    Verify if the system runs or permits execution of third-party applications without sandboxing restrictions
    Affected if Applications can be executed outside the macOS App Sandbox without additional restrictions
  4. Assess user privilege context
    Review which user accounts have administrative privileges via System Preferences > Users & Groups
    Affected if Standard or low-privilege users exist on the system who could be targeted for privilege escalation

The system is affected if it runs macOS Big Sur 11.0 to 11.6.5 or Monterey 12.0.0 to 12.3, since these versions contain the vulnerable input validation logic that could allow a malicious application to perform an out-of-bounds read and escalate privileges.

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

Update macOS devices to Monterey 12.4 or later, or Big Sur 11.6.6 or later, to incorporate the fixed input validation logic that addresses this out-of-bounds read vulnerability.

Recommended fix High confidence

macOS Big Sur 11.6.6 or macOS Monterey 12.4 (depending on your base OS)

  1. Check the current macOS version by clicking the Apple menu > About This Mac
  2. Back up important data using Time Machine or another backup solution
  3. For macOS Big Sur (11.x) users: Install macOS Big Sur 11.6.6 by going to System Preferences > Software Update, or download from the Mac App Store
  4. For macOS Monterey (12.x) users: Install macOS Monterey 12.4 by going to System Preferences > Software Update, or download from the Mac App Store
  5. Restart the computer when prompted to complete the installation
  6. Verify the update was successful by checking the macOS version in About This Mac

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26718 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