CVE-2026-43772
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 · uneditedA path traversal issue was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6. An app may be able to break out of its sandbox.
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 path traversal vulnerability in macOS allows an application to escape its sandbox restrictions. The issue was remediated through improved input validation, preventing malicious apps from accessing files outside their permitted directory. This could enable a locally-installed app to read or modify sensitive system files.
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>= 14.0, < 14.8.8>= 15.0, < 15.7.8>= 26.0, < 26.6CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/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.
-
Check installed macOS version using sw_versRun the command `sw_vers` in Terminal and note the value in the "ProductVersion" field (e.g., 14.7.2, 15.5.1, 26.3)Affected if The version falls within 14.0 to 14.8.7, 15.0 to 15.7.7, or 26.0 to 26.5 (any version below the fixed releases)
-
Check macOS version from System SettingsOpen System Settings > General > About and read the macOS version displayedAffected if The displayed version is below 14.8.8 for Sonoma, below 15.7.8 for Sequoia, or below 26.6 for Tahoe
-
Confirm the specific release number (optional)Run `sw_vers -buildVersion` to see the exact build, which can help differentiate between security update levelsAffected if The build version is older than the builds containing the security fixes (builds for 14.8.8, 15.7.8, or 26.6)
You are affected if your macOS version is 14.0 through 14.8.7 (Sonoma), 15.0 through 15.7.7 (Sequoia), or 26.0 through 26.5 (Tahoe), as these contain the vulnerable input validation in the path traversal component.
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 · scoped14.8.815.7.826.6
Apply the macOS security updates: Sequoia 15.7.8, Sonoma 14.8.8, or Tahoe 26.6 depending on the macOS version in use.
macOS Sonoma 14.8.8 / macOS Sequoia 15.7.8 / macOS Tahoe 26.6 (depending on current version)
- Check the current macOS version by clicking the Apple menu > About This Mac
- If running macOS 14.x (Sonoma), upgrade to version 14.8.8 or later
- If running macOS 15.x (Sequoia), upgrade to version 15.7.8 or later
- If running macOS 26.x (Tahoe), upgrade to version 26.6 or later
- To upgrade, go to System Settings > General > Software Update and install available updates
- Alternatively, download the appropriate installer from the Mac App Store or Apple's support website
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43772 — 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-2026-43772 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