CVE-2025-43223
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 · uneditedA denial-of-service issue was addressed with improved input validation. This issue is fixed in iOS 18.6 and iPadOS 18.6, iPadOS 17.7.9, macOS Sequoia 15.6, macOS Sonoma 14.7.7, macOS Ventura 13.7.7, tvOS 18.6, visionOS 2.6, watchOS 11.6. A non-privileged user may be able to modify restricted network settings.
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 confidenceA vulnerability in Apple operating systems allows a non-privileged user to modify restricted network settings, potentially leading to denial of service or network disruption. The issue was addressed with improved input validation. Affected systems include iOS 18.6, iPadOS 17.7.9 and 18.6, macOS Sequoia 15.6, Sonoma 14.7.7, Ventura 13.7.7, tvOS 18.6, visionOS 2.6, and watchOS 11.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< 17.7.7>= 18.0, < 18.6< 18.6< 13.7.7>= 14.0, < 14.7.7>= 15.0, < 15.6< 18.6< 2.6< 11.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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device typeDetermine whether the device is an iPhone, iPad, Mac, Apple TV, Vision Pro, or Apple WatchAffected if Device is any of these Apple products
-
Check iOS or iPadOS versionOn iPhone or iPad, open Settings > General > About and note the version number (for example, 18.5 or 17.7.6)Affected if Version is less than 18.6, or version is 17.7.7 or higher but less than 18.6 (specifically < 17.7.7; >= 18.0, < 18.6)
-
Check macOS versionOn Mac, open System Settings > About (or System Preferences > About on older versions) and note the version number (for example, 15.5 or 14.7.6)Affected if Version is less than 13.7.7, or between 14.0 and 14.7.7 (exclusive), or between 15.0 and 15.6 (exclusive)
-
Check tvOS, visionOS, or watchOS versionOn Apple TV, open Settings > General > About. On Vision Pro or Apple Watch, open Settings > General > About and note the version numberAffected if tvOS version is less than 18.6; visionOS version is less than 2.6; watchOS version is less than 11.6
A user is affected if their device runs any of the listed Apple OS versions within the vulnerable ranges, which can be verified by checking the OS version in the device settings.
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.611.613.7.7
Apply vendor-supplied updates to all affected Apple devices. For enterprise environments, deploy updates via MDM (Mobile Device Management) or ensure end-users update their devices to the patched versions.
iOS 18.6 / iPadOS 18.6 / iPadOS 17.7.9 / macOS Ventura 13.7.7 / macOS Sonoma 14.7.7 / macOS Sequoia 15.6 / tvOS 18.6 / visionOS 2.6 / watchOS 11.6 (depending on device type and starting version)
- Identify the current operating system version on the affected device (iPadOS, iOS, macOS, tvOS, visionOS, or watchOS)
- For iPadOS 17.x users: Upgrade to iPadOS 17.7.9
- For iPadOS 18.x users: Upgrade to iPadOS 18.6
- For iPhone users: Upgrade to iOS 18.6
- For macOS Ventura (13.x) users: Upgrade to macOS Ventura 13.7.7
- For macOS Sonoma (14.x) users: Upgrade to macOS Sonoma 14.7.7
- For macOS Sequoia (15.x) users: Upgrade to macOS Sequoia 15.6
- For tvOS users: Upgrade to tvOS 18.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43223 — 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-43223 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