CVE-2022-26724
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 · uneditedAn authentication issue was addressed with improved state management. This issue is fixed in tvOS 15.5. A local user may be able to enable iCloud Photos without authentication.
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 a local authentication bypass vulnerability in tvOS 15.5 where improper state management allows a local user to enable iCloud Photos without proper authentication. The attacker needs local access to the Apple TV device.
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< 15.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify Apple TV devices in your environmentInventory all Apple TV devices managed by your organization. This can be done via MDM enrollment records, network scans for Apple TV device signatures, or physical inspection of devices.Affected if any Apple TV devices are present in the environment
-
Check installed tvOS versionOn each Apple TV device, navigate to Settings > General > About > Version to display the current tvOS version number. If devices are managed via MDM, check the device inventory in your MDM console for the OS version attribute.Affected if version displays 15.4 or lower (any version below 15.5)
-
Confirm device has iCloud Photos capabilityNavigate to Settings > Users and Accounts on the Apple TV to verify iCloud account configuration is present. The vulnerability affects the iCloud Photos feature specifically.Affected if an iCloud account is signed in and iCloud Photos settings are accessible on a vulnerable tvOS version
Environment is affected if any Apple TV device runs tvOS version 15.4 or lower with an iCloud account configured, as the improper state management flaw allows unauthenticated iCloud Photos access.
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.5
Upgrade tvOS to version 15.5 or later to remediate this vulnerability. Organizations managing Apple TV devices should deploy the update via MDM and verify compliance.
tvOS 15.5
- Open the Settings app on Apple TV
- Navigate to System > Software Updates
- Select "Update Software" to check for available updates
- If tvOS 15.5 is available, select "Download and Install"
- Wait for the update to download and install, then restart the device if prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26724 — 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-2022-26724 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