CVE-2025-68640: The Apple Find My backend service through 2025-12-17 allows an attacker in possession of a valid PET (Priva...
The Apple Find My backend service through 2025-12-17 allows an attacker in possession of a valid PET (Private Endpoint Token) to enumerate devices and remove offline devices from an Apple ID account without triggering two-factor authentication or ownership verification. This may result in unauthorized removal of devices associated with the account.
Security readout for executives and security teams
Plain-English summary
This CVE describes a weakness in Apple’s Find My backend where someone holding a valid Private Endpoint Token could list devices and remove offline devices from an Apple ID without additional two-factor or ownership checks. The main business risk is loss of device recovery and account trust, not broad system compromise.
Executive priority
Treat as a moderate account-security issue. Prioritize organizations that depend on Find My for recovery, loss prevention, or executive-device assurance, especially where Apple ID compromise is already a concern.
Technical view
The record describes missing or insufficient authentication checks in Apple Find My backend operations. With a valid PET, an attacker could enumerate associated devices and remove offline devices from an Apple ID account. The CVE maps to CWE-287 and CWE-306 with CVSS 3.1 score 5.3.
Likely exposure
Exposure appears limited to Apple ID accounts where an attacker has obtained a valid PET. The source bundle does not identify affected client software, CPEs, enterprise products, or local systems to patch.
Exploitation context
No CISA KEV entry or supplied source states active exploitation. Public references are listed, but the provided bundle does not establish exploitation in the wild or provide confirmed vendor remediation details.
Researcher notes
Evidence is limited to the CVE metadata and two public researcher references. The affected-product fields are n/a, and no patch is named in the supplied bundle. Avoid assuming broader Apple platform exposure without vendor confirmation.
Mitigation direction
Check Apple guidance or support channels for confirmed remediation status.
Investigate suspected Apple ID token or account compromise promptly.
Review Apple ID device lists for unexpected removals or unknown devices.
Use available Apple account security controls and rotate credentials where compromise is suspected.
Validation and detection
Confirm whether managed users rely on Apple IDs and Find My for device recovery.
Review account and device inventory records for unexplained offline device removal.
Check security monitoring for Apple ID takeover or token compromise indicators.
Track the CVE record and referenced reports for vendor updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.