VulnerabilityPublished 14 Sep 2026

CVE-2026-65355: Apple iOS and iPadOS · A website may be able to determine a user's IP address with Private Relay turned on

Affects Apple iOS and iPadOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 26.6.1 or 18.7.10 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.6.1, 18.7.10, 26.6.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade iOS and iPadOS to 26.6.1 or 18.7.10; macOS to 26.6.2; visionOS to 26.6.1.

Affected software

Product	Affected	Fixed in
AppleiOS and iPadOS	Affected <26.6.1	Fixed in 26.6.1
AppleiOS and iPadOS	Affected <18.7.10	Fixed in 18.7.10
ApplemacOS	Affected <26.6.2	Fixed in 26.6.2
ApplevisionOS	Affected <26.6.1	Fixed in 26.6.1

AI-suggested

Apply the official patches by updating to iOS 18.7.10 or later, iPadOS 18.7.10 or later, iOS 26.6.1 or later, iPadOS 26.6.1 or later, macOS Tahoe 26.6.2 or later, or visionOS 26.6.1 or later. These updates contain the fix for the information disclosure issue. No additional mitigations are required once patched.

Description

CVE-2026-65355 is an information disclosure vulnerability in Apple iOS and iPadOS where a website may be able to determine a user's IP address despite Private Relay being enabled. This issue has been addressed with improved state management and fixed in iOS 18.7.10, iPadOS 18.7.10, iOS 26.6.1, iPadOS 26.6.1, macOS Tahoe 26.6.2, and visionOS 26.6.1. The vulnerability has a medium severity rating with a CVSS score of 4.3.

Impact

The impact is limited to information disclosure of the user's IP address when Private Relay is enabled. There is no indication of integrity or availability impact. This could reduce the privacy protections expected from Private Relay but does not directly enable system compromise.

Summary

This vulnerability allows a website to potentially discover the real IP address of a user who has enabled Apple's Private Relay feature on iOS and iPadOS devices. The flaw was due to insufficient state management that could leak IP information. Apple has released official fixes in multiple OS versions including iOS 18.7.10 and 26.6.1, iPadOS 18.7.10 and 26.6.1, macOS Tahoe 26.6.2, and visionOS 26.6.1 to resolve this issue.

CWE-642External Control of Critical State Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores security-critical state information about its users, or the product itself, in a location that is accessible to unauthorized actors.
Architecture and Design
Understand all the potential locations that are accessible to attackers. For example, some programmers assume that cookies and hidden form fields cannot be modified by an attacker, or they may not consider that environment variables can be modified before a privileged program is invoked.
Architecture and Design · Attack Surface Reduction
Store state information and sensitive data on the server side only.
Architecture and Design
Store state information on the server side only. Ensure that the system definitively and unambiguously keeps track of its own state and user state and has rules defined for legitimate state transitions.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Exploitation of Trusted Identifiers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Sep 2026, 01:31 UTC

WeaknessesCWE-642

Technical details

References

Community reviews

Related threats