CVE-2023-28826
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 with improved redaction of sensitive information. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, macOS Monterey 12.7.4, macOS Sonoma 14.1, macOS Ventura 13.6.5. An app may be able to access sensitive user data.
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 information disclosure vulnerability in Apple operating systems where an application could access sensitive user data due to insufficient redaction of sensitive information. The issue allows a malicious or compromised app to bypass privacy protections and obtain user data that should have been redacted or hidden.
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< 16.7.6< 16.7.6>= 12.0, < 12.7.4>= 13.0, < 13.6.5= 14.0CVSS 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.
-
Check iOS version on iPhoneOn the device, go to Settings > General > About and note the version number shown next to 'Version'Affected if Version is lower than 16.7.6 (for example, 16.7.5 or earlier)
-
Check iPadOS version on iPadOn the device, go to Settings > General > About and note the version number shown next to 'Version'Affected if Version is lower than 16.7.6 (for example, 16.7.5 or earlier)
-
Check macOS version on MacClick the Apple menu in the top-left corner, select About This Mac, and note the version number displayed (for example, 13.5 or 14.0)Affected if Version is 12.0 through 12.7.3, 13.0 through 13.6.4, or exactly 14.0
Your device is affected if it runs any iOS/iPadOS version below 16.7.6, or any macOS version 12.0-12.7.3, 13.0-13.6.4, or 14.0.
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 · scoped12.7.413.6.516.7.6
Apply the relevant security update for the affected platform: iOS 16.7.6 and iPadOS 16.7.6 for mobile devices, macOS Monterey 12.7.4, macOS Ventura 13.6.5, or macOS Sonoma 14.1 for Mac computers.
iOS 16.7.6 / iPadOS 16.7.6 / macOS 12.7.4 / macOS 13.6.5 / macOS 14.1
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 16.7.6 or iPadOS 16.7.6
- For macOS Monterey (12.x): Go to System Settings > General > Software Update and install macOS 12.7.4
- For macOS Ventura (13.x): Go to System Settings > General > Software Update and install macOS 13.6.5
- For macOS Sonoma (14.0): Go to System Settings > General > Software Update and install macOS 14.1
- After updating, verify the version in Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28826 — 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-2023-28826 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