CVE-2025-24270
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 by removing the vulnerable code. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4. An attacker on the local network may be able to leak sensitive user information.
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 · low confidenceThis is an Apple vulnerability affecting iOS, iPadOS, macOS, tvOS, and visionOS where an attacker on the local network may be able to leak sensitive user information. The specific vulnerable code was removed in the patched versions.
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.6>= 18.0, < 18.4< 18.4< 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4< 18.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/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.
-
Identify device and operating systemDetermine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Vision Pro, and note the installed operating system name and version number.Affected if Device runs iOS, iPadOS, macOS, tvOS, or visionOS and the specific version falls within the affected ranges.
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About to view the version number. Compare the installed version to: iOS < 18.4, or iPadOS < 17.7.6, or iPadOS >= 18.0 and < 18.4.Affected if The device runs iOS < 18.4 or iPadOS < 17.7.6, or iPadOS 18.0 to 18.3.x.
-
Check macOS versionOn Mac, go to System Settings > About or use the Apple menu > About This Mac to view the version number. Compare against: macOS < 13.7.5, macOS 14.0 to 14.7.4, or macOS 15.0 to 15.3.x.Affected if The Mac runs any of the three affected version ranges: Ventura below 13.7.5, Sonoma below 14.7.5, or Sequoia below 15.4.
-
Check tvOS or visionOS versionOn Apple TV, go to Settings > General > About to see the version. On Apple Vision Pro, go to Settings > General > About. Compare tvOS to < 18.4 and visionOS to < 2.4.Affected if The device runs tvOS earlier than 18.4 or visionOS earlier than 2.4.
-
Assess network exposureDetermine if the device is connected to a network where untrusted or unauthorized devices could access the local network. This includes shared Wi-Fi networks, guest networks, or networks with unknown devices.Affected if The vulnerable device is on a network where an attacker could gain local network access.
The device is affected if it runs any iOS, iPadOS, macOS, tvOS, or visionOS version earlier than the patched releases (iOS/iPadOS 18.4 or 17.7.6, macOS 15.4/14.7.5/13.7.5, tvOS 18.4, visionOS 2.4) AND is connected to a network where an untrusted local attacker could be present.
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.413.7.514.7.5
Apply the security updates: iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, or visionOS 2.4.
iOS 18.4, iPadOS 17.7.6 or 18.4, macOS Ventura 13.7.5, macOS Sonoma 14.7.5, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4
- For iPhone: Back up your device, then go to Settings > General > Software Update and install iOS 18.4
- For iPad: Back up your device, then go to Settings > General > Software Update and install iPadOS 18.4 (or iPadOS 17.7.6 if on older major version)
- For Mac: Back up your device, then go to System Settings > General > Software Update and install macOS 13.7.5 (Ventura), 14.7.5 (Sonoma), or 15.4 (Sequoia) depending on your current version
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4
- For Apple Vision Pro: Go to Settings > General > Software Updates and install visionOS 2.4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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-2025-24270 — 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-24270 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