CVE-2022-26712
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 · uneditedThis issue was addressed by removing the vulnerable code. This issue is fixed in macOS Monterey 12.4, macOS Big Sur 11.6.6. A malicious application may be able to modify protected parts of the file system.
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 privilege escalation vulnerability in macOS that allowed a malicious application to modify protected parts of the file system. The vulnerable code was removed in the fix versions macOS Monterey 12.4 and Big Sur 11.6.6.
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.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Identify installed macOS versionRun 'sw_vers -productVersion' in Terminal or check System Preferences > About This MacAffected if The command returns a version number
-
Determine if running macOS Big SurIf version starts with 11.x, this is Big SurAffected if Version is 11.x and less than 11.6.6
-
Determine if running macOS MontereyIf version starts with 12.x, this is MontereyAffected if Version is 12.x and less than 12.4
-
Compare against affected version rangesCheck if version falls in 11.0 <= version < 11.6.6 OR 12.0.0 <= version < 12.4Affected if Version matches either of these ranges indicates the vulnerable code is present
If macOS version is 11.0 to 11.6.5 (Big Sur) or 12.0.0 to 12.3 (Monterey), the system is affected by this vulnerability.
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 security update by upgrading to macOS Monterey 12.4 or later, or Big Sur 11.6.6 or later. No custom code remediation is required as this is a patch management issue.
macOS Big Sur 11.6.6 or later, or macOS Monterey 12.4 or later
- Back up important data before performing any system update
- Go to System Preferences (or System Settings on macOS Ventura and later)
- Click on Software Update
- Allow the system to check for available updates
- If macOS Big Sur 11.0 to 11.6.5 is installed, update to macOS Big Sur 11.6.6 or later
- If macOS Monterey 12.0 to 12.3 is installed, update to macOS Monterey 12.4 or later
- Restart the system if prompted
- 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.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26712 — 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-26712 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