dbcve.org
ItunesApplication · Apple

CVE-2022-26751

HIGH · 7.8 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 10.15.7 / 11.6.6 or later.
See remediation →
81/100
Remediation priority · High
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
A memory corruption issue was addressed with improved input validation. This issue is fixed in iTunes 12.12.4 for Windows, iOS 15.5 and iPadOS 15.5, Security Update 2022-004 Catalina, macOS Big Sur 11.6.6, macOS Monterey 12.4. Processing a maliciously crafted image may lead to arbitrary code execution.

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 corruption vulnerability in Apple's image processing components allows arbitrary code execution when a user processes a maliciously crafted image. The vulnerability was addressed through improved input validation, preventing the memory corruption that could be exploited.

MitigationApply the available security updates: iOS 15.5, iPadOS 15.5, macOS Monterey 12.4, macOS Big Sur 11.6.6, Security Update 2022-004 Catalina, or iTunes 12.12.4 for Windows, depending on the affected platform.

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
ItunesApplication
Affected:< 12.12.4
IpadosOperating system
Affected:< 15.5
Iphone OsOperating system
Affected:< 15.5
Mac Os XOperating system
Affected:< 10.15.7= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.6.6>= 12.0, < 12.4

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 product type
    Determine whether you are running iTunes (Windows), iPadOS, iOS, or macOS on your device. This will determine which version range applies to your installation.
    Affected if You are running any of the affected Apple products listed in the CVE.
  2. Check iTunes version on Windows
    Open iTunes, then go to Help > About iTunes to view the installed version number.
    Affected if The version displayed is less than 12.12.4.
  3. Check iOS or iPadOS version
    On your iPhone or iPad, go to Settings > General > About and view the Version field.
    Affected if The version is less than 15.5.
  4. Check macOS version
    Click the Apple menu and select About This Mac. The version number will be displayed under the macOS name.
    Affected if The version is 10.15.7 (any build), or falls in the range 11.0 to 11.6.5, or 12.0 to 12.3.

You are affected if your installed version falls below the minimum fixed version for your specific Apple platform and OS.

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 10.15.7 / 11.6.6 / 12.4 or later
Fixed in 10.15.711.6.612.4
Interim mitigation

Apply the available security updates: iOS 15.5, iPadOS 15.5, macOS Monterey 12.4, macOS Big Sur 11.6.6, Security Update 2022-004 Catalina, or iTunes 12.12.4 for Windows, depending on the affected platform.

Recommended fix High confidence

iTunes 12.12.4 (Windows); iOS 15.5; iPadOS 15.5; macOS Big Sur 11.6.6; macOS Monterey 12.4; Security Update 2022-004 Catalina

  1. For iTunes on Windows: Download and install iTunes 12.12.4 from the official Apple website or Microsoft Store
  2. For iOS devices: Go to Settings > General > Software Update and install iOS 15.5
  3. For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 15.5
  4. For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.6.6
  5. For macOS Monterey (12.x): Go to System Preferences > Software Update and install macOS Monterey 12.4
  6. For macOS Catalina (10.15.7): Install Security Update 2022-004 Catalina via System Preferences > Software Update
Caveat Standard Apple update; review release notes for any functionality changes

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

Fix this in Itunes Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26751 — 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-2022-26751 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