CVE-2025-30448
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 additional entitlement checks. This issue is fixed in iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.4, macOS Sonoma 14.7.6, macOS Ventura 13.7.6, visionOS 2.5. An attacker may be able to turn on sharing of an iCloud folder without authentication.
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 · high confidenceThis is an authentication bypass vulnerability in Apple's iCloud folder sharing feature. An attacker can enable sharing of an iCloud folder without proper authentication, likely due to missing or insufficient entitlement validation checks in the sharing workflow. The fix involves additional entitlement checks to verify the user is properly authenticated before allowing sharing settings to be modified.
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< 17.7.7>= 18.0, < 18.5< 18.5< 13.7.6>= 14.0, < 14.7.6>= 15.0, < 15.4< 2.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Check iOS version on iPhoneGo to Settings > General > About and note the version number (e.g., 18.4). Alternatively, run 'sw_vers' via SSH or mobile device management.Affected if Version is less than 18.5 (any 18.x version below 18.5) or is between 18.0 and 18.4 inclusive.
-
Check iPadOS version on iPadGo to Settings > General > About and note the version number. Alternatively, run 'sw_vers' via SSH or MDM.Affected if Version is less than 17.7.7, or is 18.0 through 18.4 (any version below 18.5), or is 18.0 through 18.4.
-
Check macOS versionGo to System Settings > About (or Apple menu > About This Mac) and note the version number. Alternatively, run 'sw_vers' in Terminal.Affected if Version is less than 13.7.6, or is 14.0 through 14.7.5, or is 15.0 through 15.3.
-
Check visionOS versionGo to Settings > General > About and note the version number.Affected if Version is less than 2.5.
-
Verify iCloud folder sharing is configuredCheck if any iCloud folders are set up for sharing. On macOS: open Finder > iCloud Drive > look for shared folders. On iOS/iPadOS: open Files app > iCloud Drive > look for shared folders.Affected if Any iCloud folders are currently shared with others (the vulnerability affects the sharing enablement process, so this feature must be in use).
The device is affected if its operating system version falls within any of the vulnerable ranges listed AND the iCloud folder sharing feature is enabled or used.
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.513.7.614.7.6
Apply the security updates for affected Apple operating systems: iOS 18.5, iPadOS 18.5/17.7.7, macOS Sequoia 15.4, Sonoma 14.7.6, Ventura 13.7.6, and visionOS 2.5. For enterprise environments, deploy these updates via MDM or software distribution tools.
iOS 18.5 / iPadOS 18.5 / iPadOS 17.7.7 / macOS Ventura 13.7.6 / macOS Sonoma 14.7.6 / macOS Sequoia 15.4 / visionOS 2.5 (depending on current device and OS)
- Identify the Apple device type (iPhone, iPad, Mac, or Apple Vision) and current OS version
- For iPhone: Upgrade to iOS 18.5
- For iPad: If currently on iPadOS 18.x, upgrade to iPadOS 18.5; if on iPadOS 17.x, upgrade to iPadOS 17.7.7
- For Mac: Determine the macOS version (Ventura, Sonoma, or Sequoia) and upgrade to the corresponding fixed version: Ventura to 13.7.6, Sonoma to 14.7.6, Sequoia to 15.4
- For Apple Vision: Upgrade to visionOS 2.5
- Verify the upgrade was successful by checking the OS version in Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30448 — 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-30448 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