CVE-2022-26756
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 out-of-bounds write issue was addressed with improved input validation. This issue is fixed in Security Update 2022-004 Catalina, macOS Monterey 12.4, macOS Big Sur 11.6.6. 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 · moderate confidenceAn out-of-bounds write vulnerability in macOS kernel allows a local application to escalate privileges to kernel level. The issue was addressed with improved input validation in the affected macOS versions.
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< 10.15.7= 10.15.7>= 11.0, < 11.6.6>= 12.0, < 12.4CVSS 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.
-
Determine installed macOS versionRun 'sw_vers -productVersion' in Terminal to get the exact version number (e.g., 12.3, 11.6.5, 10.15.7)Affected if Version is 10.15.7 or any version before 10.15.7, OR between 11.0 and 11.6.5 inclusive, OR between 12.0 and 12.3 inclusive
-
Confirm kernel-level access is possibleThis vulnerability allows a local application to write to kernel memory. Verify if untrusted local applications can be executed on the system.Affected if Untrusted local applications can be run and the macOS version falls within the affected ranges above
A system is affected if it runs macOS 10.15.7 or earlier, macOS 11.0-11.6.5, or macOS 12.0-12.3 and allows execution of local applications.
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 · scoped10.15.711.6.612.4
Apply the appropriate macOS security update: Security Update 2022-004 for Catalina, macOS 12.4 for Monterey, or macOS 11.6.6 for Big Sur.
Security Update 2022-004 Catalina / macOS Big Sur 11.6.6 / macOS Monterey 12.4
- Open System Preferences (or System Settings on macOS Ventura and later)
- Click on 'Software Update' to check for available updates
- Install Security Update 2022-004 Catalina (for macOS 10.15.7)
- Install macOS Big Sur 11.6.6 (for macOS 11.x)
- Install macOS Monterey 12.4 (for macOS 12.x)
- Restart the system after applying the update
- Verify the update was installed by checking System Preferences > About > Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26756 — 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-26756 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