CVE-2026-28941
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 improved checks. This issue is fixed in iOS 18.7.9 and iPadOS 18.7.9, macOS Sequoia 15.7.7, macOS Tahoe 26.5. Processing a maliciously crafted file may lead to a denial-of-service or potentially disclose memory contents.
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 confidenceThis is a file parsing vulnerability in Apple operating systems where processing a maliciously crafted file can trigger a denial-of-service condition or potentially expose memory contents. The fix involved implementing improved input validation checks during file processing.
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< 18.7.9< 18.7.9>= 15.0, < 15.7.7>= 26.0, < 26.5CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/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.
-
Identify your Apple device operating systemOn iOS/iPadOS go to Settings > General > About; on macOS go to System Settings > About or use 'sw_vers' in TerminalAffected if The device runs iOS, iPadOS, or macOS
-
Check iOS or iPadOS version numberLook at the 'Version' field in Settings > General > About. On Mac, if running macOS 15.x check System Settings > About > VersionAffected if Version is below 18.7.9 for iOS or iPadOS, or between 15.0 and 15.7.6 for macOS
-
Check macOS version if running macOS 26 or laterUse 'sw_vers -productVersion' in Terminal or check System Settings > About > VersionAffected if macOS version is 26.0 through 26.4.x (any version >= 26.0 but < 26.5)
-
Confirm file processing usageReview whether the device is used to open or parse files from untrusted sources such as email attachments, downloaded files, or third-party appsAffected if Untrusted files are processed on a vulnerable version
You are affected if your device runs iOS or iPadOS below 18.7.9, or macOS 15.0-15.7.6, or macOS 26.0-26.4.x and processes untrusted files.
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 · scoped15.7.718.7.926.5
Apply the available security updates: iOS 18.7.9, iPadOS 18.7.9, macOS Sequoia 15.7.7, or macOS Tahoe 26.5 depending on the affected device. Restrict processing of untrusted files until patches are deployed.
iOS 18.7.9, iPadOS 18.7.9, macOS Sequoia 15.7.7, or macOS Tahoe 26.5 depending on device type
- For iPhone or iPad: Back up your device, then go to Settings > General > Software Update and install iOS 18.7.9 or iPadOS 18.7.9
- For Mac: Back up your system, then go to System Settings > General > Software Update and install macOS Sequoia 15.7.7 or macOS Tahoe 26.5
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28941 — 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-28941 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