SafariWeb browser · Apple
CVE-2025-43327
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 by adding additional logic. This issue is fixed in Safari 26, macOS Tahoe 26. Visiting a malicious website may lead to address bar spoofing.
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 · moderate confidenceThis is an address bar spoofing vulnerability in Safari 26 and macOS Tahoe 26. A malicious website can manipulate the browser's address bar to display a different URL than the one the user is actually visiting, potentially enabling phishing attacks. The issue was addressed by adding additional validation logic in the browser.
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
< 26.0< 26.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/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.
-
Check Safari versionOpen Safari, then go to Safari > About Safari. Alternatively, run `defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString` in Terminal.Affected if The version displayed is earlier than 26.0 (for example, 25.4 or lower)
-
Check macOS versionClick the Apple menu > About This Mac, or run `sw_vers -productVersion` in Terminal.Affected if The macOS version is earlier than 26.0 (for example, 25.3, 25.2, or earlier)
-
Confirm the Safari build matches the macOS expectationIn Safari > About Safari, note both the version number and the build number. On macOS Tahoe 26, Safari 26 should be included by default.Affected if Running macOS below 26.0 with any Safari version, or if Safari appears downgraded from the expected 26.x bundle
You are affected if either your Safari installation is earlier than version 26.0 OR your macOS is earlier than version 26.0, since the vulnerability exists in these unpatched version ranges.
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 · scoped26.0
Update to Safari 26 or macOS Tahoe 26 (or later) to receive the security fix. Users should be advised to keep their browsers and operating systems updated.
Safari 26 / macOS Tahoe 26
- Open System Settings (or System Preferences on older macOS versions)
- Navigate to General > Software Update
- Check for available updates
- Install macOS Tahoe 26 (which includes Safari 26)
- Restart your Mac if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43327 — 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-43327 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