CVE-2022-26767
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 · uneditedThe issue was addressed with additional permissions checks. This issue is fixed in macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to bypass Privacy preferences.
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 confidenceA local permissions bypass vulnerability in macOS allowed a malicious application to circumvent Privacy preferences protections. The fix introduced additional permission checks before granting access to protected user data categories controlled by Privacy preferences (such as contacts, photos, location, or similar sensitive resources).
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>= 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 versionOpen Terminal and run: sw_vers -productVersionAffected if The version is 11.0 to 11.6.5 (Big Sur) or 12.0 to 12.3 (Monterey)
-
Confirm macOS build numberOpen Terminal and run: uname -a to see kernel version, or System Preferences > About to verify the full version stringAffected if Build date is prior to the security update release dates for this CVE (June 2022 for 12.4, July 2022 for 11.6.6)
-
Check system update statusOpen System Preferences > Software Update to see if updates are pending or if the system shows it is up to dateAffected if System reports no updates available but version falls within affected range, indicating unpatched state
The environment is affected if the installed macOS version falls within 11.0 to 11.6.5 or 12.0 to 12.3 and has not received the corresponding security updates.
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 · scoped11.6.612.4
Apply the vendor-supplied macOS updates: upgrade to macOS Monterey 12.4 or later, or macOS Big Sur 11.6.6 or later. No additional configuration required beyond standard OS patching.
macOS Big Sur 11.6.6 or later (for 11.x); macOS Monterey 12.4 or later (for 12.x)
- 1. Back up your Mac using Time Machine or another backup solution
- 2. Connect your Mac to power to ensure the update completes
- 3. Open System Preferences (or System Settings on macOS Ventura+)
- 4. Click on Software Update
- 5. Click "Update Now" or "Upgrade Now" to install macOS Big Sur 11.6.6 (for 11.x systems) or macOS Monterey 12.4 (for 12.x systems)
- 6. Follow the on-screen instructions to complete the installation
- 7. Restart your Mac when prompted
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-26767 — 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-26767 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