SafariWeb browser · Apple
CVE-2025-43229
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 through improved state management. This issue is fixed in Safari 18.6, macOS Sequoia 15.6. Processing maliciously crafted web content may lead to universal cross site scripting.
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 universal cross-site scripting (UXSS) vulnerability in Safari where maliciously crafted web content can bypass same-origin restrictions through improper state management, allowing execution of JavaScript in the context of any website. The vulnerability is fixed in Safari 18.6 and macOS Sequoia 15.6.
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
SafariWeb browser
< 18.6< 15.6CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Check installed Safari versionOpen Safari, go to Safari menu > About Safari, or navigate to apple.com/safari in the browser to see the version displayedAffected if The displayed version is any version lower than 18.6
-
Check macOS versionClick the Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if The macOS version is any version lower than 15.6 (Sequoia 15.6)
-
Verify Safari update availabilityOpen the App Store app > Updates tab, or run 'softwareupdate --list' in Terminal to see if Safari 18.6 or later is availableAffected if Safari 18.6 or later is listed as an available update, indicating an older version is installed
The environment is affected if Safari is below version 18.6 or if running macOS below version 15.6, since these versions contain the fix for the same-origin restriction bypass.
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 · scoped15.618.6
Apply the vendor-supplied patch by updating Safari to version 18.6 or later and macOS to Sequoia 15.6 or later.
Safari 18.6 or macOS Sequoia 15.6
- Open System Settings (or System Preferences on older macOS)
- Go to General > Software Update
- Click "Check for Update" or allow automatic updates
- If Safari update is available, click "Update" next to Safari 18.6
- If macOS update is available, click "Update" next to macOS Sequoia 15.6
- Restart the system if prompted to complete the installation
- Verify Safari version is 18.6 or later by clicking Safari > About Safari
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-43229 — 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-43229 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