CVE-2025-31199
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 logging issue was addressed with improved data redaction. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, macOS Sonoma 14.8.2, visionOS 2.4. 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 confidenceA vulnerability in Apple logging mechanisms allowed sensitive user data to be exposed through incomplete data redaction. The issue existed in iOS, iPadOS, macOS, and visionOS where logged data may have contained sensitive information that should have been redacted, potentially allowing malicious applications to access this data.
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.4< 18.4< 15.4< 2.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 iOS version on iPhoneGo to Settings > General > About and note the version number shown next to Software VersionAffected if Version is below 18.4 (for example, 18.3.x or earlier)
-
Check iPadOS version on iPadGo to Settings > General > About and note the version number shown next to Software VersionAffected if Version is below 18.4 (for example, 18.3.x or earlier)
-
Check macOS versionClick the Apple menu in the top-left corner, select About This Mac, and note the version number under macOSAffected if Version is below 15.4 (for example, 15.3.x or earlier)
-
Check visionOS versionGo to Settings > General > About and note the version number shown next to Software VersionAffected if Version is below 2.4 (for example, 2.3.x or earlier)
A device is affected if it runs iOS, iPadOS, macOS, or visionOS and the installed version is lower than the patched release (18.4, 15.4, or 2.4 respectively).
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 · scoped2.415.418.4
Update affected devices to iOS 18.4/iPadOS 18.4, macOS Sequoia 15.4, macOS Sonoma 14.8.2, or visionOS 2.4 to apply the improved data redaction in logging functions.
iOS 18.4 / iPadOS 18.4 / macOS Sequoia 15.4 / macOS Sonoma 14.8.2 / visionOS 2.4
- Back up your device data before performing any update
- Ensure device is connected to Wi-Fi and has sufficient battery charge (or is plugged into power)
- On iOS/iPadOS: Navigate to Settings > General > Software Update and download/install iOS 18.4 or iPadOS 18.4
- On macOS: Navigate to System Settings > General > Software Update and download/install macOS Sequoia 15.4 or macOS Sonoma 14.8.2
- On visionOS: Navigate to Settings > General > Software Update and download/install visionOS 2.4
- Restart the device after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31199 — 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-31199 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