CVE-2025-24180
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 · uneditedThe issue was addressed with improved input validation. This issue is fixed in Safari 18.4, iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4. A malicious website may be able to claim WebAuthn credentials from another website that shares a registrable suffix.
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 a WebAuthn authentication bypass vulnerability where a malicious website can steal (claim) WebAuthn credentials from another website that shares the same registrable suffix (eTLD+1). The fix in Safari 18.4 and other Apple OS updates implements improved input validation to properly enforce origin separation between sites.
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< 18.4>= 15.0, < 15.4< 2.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Safari version on macOSOpen Safari, go to Safari > About Safari to view the version numberAffected if Version is less than 18.4 and you use WebAuthn for authentication on any website
-
Check macOS versionClick Apple menu > About This Mac to see the macOS versionAffected if macOS version is 15.0, 15.1, 15.2, or 15.3 (shown as 15.x) and you use WebAuthn for authentication on any website
-
Check iOS or iPadOS versionGo to Settings > General > About on iPhone or iPad to view the iOS versionAffected if Version is less than 18.4 and you use WebAuthn for authentication on any website
-
Check visionOS versionGo to Settings > General > About on Apple Vision to view the versionAffected if Version is less than 2.3 and you use WebAuthn for authentication on any website
-
Verify WebAuthn credential usageCheck your browser's credential manager or review your relying party applications for WebAuthn/WebCrypto credential registrationsAffected if You have WebAuthn credentials registered on websites - the vulnerability allows theft of these credentials by malicious sites sharing the same eTLD+1 (e.g., attacker on evil.example.com stealing credentials from legit.example.com)
You are affected if any Apple device/browser you use runs Safari < 18.4, iOS/iPadOS < 18.4, macOS 15.0-15.3, or visionOS < 2.3 AND you authenticate using WebAuthn on websites that share an eTLD+1 with other sites you visit.
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.315.418.4
Ensure all user devices are updated to the fixed versions (Safari 18.4, iOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4) to remediate this cross-site credential theft vulnerability.
Safari 18.4, iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, visionOS 2.4, watchOS 11.4
- For Safari on macOS: Open the App Store, click Updates, and install Safari 18.4
- 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
- For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.4
- For Apple Vision: Go to Settings > General > Software Update and install visionOS 2.4
- For Apple Watch: Go to Settings > General > Software Update on the paired iPhone, or on Watch go to Settings > General > Software Update, and install watchOS 11.4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24180 — 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-24180 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