dbcve.org
IpadosOperating system · Apple

CVE-2026-28903

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 18.7.9 / 26.5 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The issue was addressed with improved memory handling. This issue is fixed in Safari 26.5, iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5. Processing maliciously crafted web content may lead to an unexpected process crash.

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 confidence

A memory handling vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected process crash. This affects Safari and web rendering components across multiple Apple platforms.

MitigationUpdate affected Apple devices to the specified patched versions (Safari 26.5, iOS/iPadOS 18.7.9 or 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5) to remediate this vulnerability.

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
IpadosOperating system
Affected:< 18.7.9>= 26.0, < 26.5
Iphone OsOperating system
Affected:< 18.7.9>= 26.0, < 26.5
macOSOperating system
Affected:>= 26.0, < 26.5
TvosOperating system
Affected:< 26.5
VisionosOperating system
Affected:< 26.5
WatchosOperating system
Affected:< 26.5

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apple device type
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch
    Affected if The device runs any of the affected Apple operating systems listed in the CVE
  2. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number
    Affected if The version is below 18.7.9 OR is 26.0 or higher but below 26.5
  3. Check the installed macOS version
    On Mac, click the Apple menu > About This Mac and note the version number
    Affected if The version is 26.0 or higher but below 26.5
  4. Check the Safari version on macOS
    On Mac, open Safari > About Safari and note the version number
    Affected if Safari version is below 26.5 (independent check for Mac users who may have OS-level but older Safari updates)
  5. Check tvOS, visionOS, or watchOS version
    On Apple TV, Apple Vision Pro, or Apple Watch, go to Settings > General > About and note the version number
    Affected if The version is below 26.5

You are affected if your device runs any OS version within the ranges specified: iOS/iPadOS < 18.7.9 or >= 26.0 to < 26.5, macOS >= 26.0 to < 26.5, or tvOS/visionOS/watchOS < 26.5

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.7.9 / 26.5 or later
Fixed in 18.7.926.5
Interim mitigation

Update affected Apple devices to the specified patched versions (Safari 26.5, iOS/iPadOS 18.7.9 or 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5) to remediate this vulnerability.

Recommended fix High confidence

iOS 18.7.9 or iOS 26.5 (depending on branch); iPadOS 18.7.9 or iPadOS 26.5; macOS Tahoe 26.5; tvOS 26.5; visionOS 26.5; watchOS 26.5

  1. Check current iOS version by going to Settings > General > About > Version
  2. Check current iPadOS version by going to Settings > General > About > Version
  3. Check current macOS version by clicking Apple menu > About This Mac
  4. Check current tvOS version by going to Settings > General > About > Version
  5. Check current visionOS version by going to Settings > General > About > Version
  6. Check current watchOS version by going to Settings > General > About > Version
  7. For iOS/iPadOS: If on 18.x branch, upgrade to iOS 18.7.9 or later; if on 26.x branch, upgrade to iOS 26.5 or later
  8. For macOS: Upgrade to macOS Tahoe 26.5 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28903 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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