CVE-2025-24271
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 · uneditedAn access issue was addressed with improved access restrictions. 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 unauthenticated user on the same network as a signed-in Mac could send it AirPlay commands without pairing.
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 access control bypass in AirPlay where an unauthenticated attacker on the same local network as a signed-in Mac can send AirPlay commands without completing the required pairing/authentication process. The vulnerability stems from insufficient verification that incoming AirPlay commands originate from properly paired devices.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 your device type and OSDetermine if the device is a Mac, iPhone, iPad, Apple TV, or Apple Vision Pro. On Mac, run 'sw_vers -productVersion'. On iPhone/iPad, go to Settings > General > About. On Apple TV, go to Settings > General > About. On Vision Pro, go to Settings > General > About.Affected if Device runs any of the affected Apple operating systems (macOS, iOS, iPadOS, tvOS, visionOS)
-
Check macOS version against affected rangesRun 'sw_vers -productVersion' or view System Settings > General > About. Compare the version to: < 13.7.5; >= 14.0, < 14.7.5; >= 15.0, < 15.4Affected if Version falls within any of these ranges: 13.0-13.7.4, 14.0-14.7.4, or 15.0-15.3
-
Check iOS/iPadOS version against affected rangesGo to Settings > General > About on iPhone or iPad. Compare the version to: < 17.7.6; >= 18.0, < 18.4 for iPadOS; < 18.4 for iOSAffected if iPadOS version is 17.0-17.7.5 or 18.0-18.3; iOS version is any version below 18.4
-
Check tvOS version against affected rangesGo to Settings > General > About on Apple TV. Compare the version to: < 18.4Affected if tvOS version is any version below 18.4
-
Check visionOS version against affected rangesGo to Settings > General > About on Apple Vision Pro. Compare the version to: < 2.4Affected if visionOS version is any version below 2.4
-
Verify AirPlay receiver is enabled (for macOS)On Mac, open System Settings > AirPlay > AirPlay receiver. Check if the feature is turned ON.Affected if AirPlay receiver is enabled and OS version is in the affected ranges listed above
The environment is affected if the device runs any macOS version below 13.7.5, 14.0-14.7.4, or 15.0-15.3; any iOS below 18.4; any iPadOS below 17.7.6 or 18.0-18.3; any tvOS below 18.4; or any visionOS below 2.4, AND has AirPlay functionality enabled.
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 vendor patches (iOS 18.4/iPadOS 18.4/17.7.6, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.4, visionOS 2.4). As a compensating control, restrict network access to trusted devices only and disable AirPlay when not in use.
iOS 18.4 / iPadOS 18.4 / iPadOS 17.7.6 / macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 / tvOS 18.4 / visionOS 2.4
- Back up your device data before performing any system update
- For iPhone: Go to Settings > General > Software Update and install iOS 18.4
- For iPad: Go to Settings > General > Software Update and install iPadOS 18.4 (or 17.7.6 if staying on iOS 17)
- For Mac: Open System Settings > General > Software Update and install the appropriate macOS version (Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4)
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4
- After updating, verify the update was successful by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24271 — 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-24271 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