CVE-2025-30435
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 macOS Sequoia 15.4. A sandboxed app may be able to access sensitive user data in system logs.
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 sandboxed macOS application could access sensitive user data that should have been redacted from system logs, allowing potential privacy violations through log file inspection.
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>= 15.0, < 15.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.
-
Check installed macOS versionOpen System Settings > General > About, or run 'sw_vers' in TerminalAffected if The version shown is 15.0, 15.1, 15.2, or 15.3.x (any version >= 15.0 but < 15.4)
-
Confirm macOS Sequoia releaseVerify the macOS name is 'Sequoia' in System Settings > General > About next to the version numberAffected if The system is running macOS Sequoia (required for this vulnerability to apply)
-
Identify if sandboxed apps have log accessReview system log files in /var/log or via Console.app for entries from third-party sandboxed applications that may contain sensitive user dataAffected if Sandboxed applications have been able to read logs containing unreduced sensitive information (this is the vulnerable behavior)
You are affected if your Mac runs macOS Sequoia version 15.0 through 15.3.x, as these versions contain the log redaction flaw that allows sandboxed apps to access sensitive user data in system logs.
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.4
Update to macOS Sequoia 15.4 or later to receive the improved redaction of sensitive information in system logs.
macOS Sequoia 15.4
- Back up your Mac using Time Machine before starting the update
- Connect your Mac to power to ensure the update isn't interrupted
- Open System Settings → General → Software Update
- Click 'Check for Update' and wait for macOS Sequoia 15.4 to appear
- Download and install macOS Sequoia 15.4
- Restart your Mac when prompted to complete the installation
- After restarting, verify the update by going to System Settings → General → About and confirming the version shows 15.4
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-2025-30435 — 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-2025-30435 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