A public proof-of-concept has appeared for CVE-2026-84636, an information-disclosure issue described as “Wi-Fi SSID Info Disclosure.” The PoC, written in Objective-C, demonstrates a case where the identifier of the currently joined wireless network — the SSID — can be read in a context where platform privacy controls are supposed to keep it out of reach.
Why an SSID is privacy-sensitive
On Apple’s platforms, reading the name of the Wi-Fi network a device is connected to is deliberately treated as sensitive. The classic API for it (CNCopyCurrentNetworkInfo) has been progressively locked down over successive releases: an app now generally needs the Access WiFi Information entitlement, an appropriate Location Services authorization, and in some cases to be the active foreground app before the system will return a real SSID rather than a placeholder.
The reason for those gates is simple: an SSID is a strong contextual signal. A network name can reveal where a person is — a home, a specific office, a named venue, an airline cabin — and a stream of SSIDs over time can be used to infer movement, correlate home and work, or help de-anonymize a user. Anything that lets code recover the SSID without clearing those permission checks is a crossing of a privacy boundary, even when it does not expose traffic contents or credentials.
What the proof-of-concept shows
The published PoC is a minimal Objective-C program that exercises the disclosure path and surfaces the network identifier that the permission model is meant to protect. In keeping with responsible-disclosure practice, this write-up stays at the conceptual level and does not reproduce the exploit code — readers who want the technical artifact can review it directly in the researcher’s repository, linked below.
Impact
This is a confidentiality issue, not a remote-code-execution or credential-theft one. The practical risk is privacy: an application (or embedded code) that should not be able to see the current SSID can obtain it anyway, bypassing the consent and entitlement model the user and the platform rely on. For privacy-conscious users and for anyone whose location is itself sensitive, that is a meaningful leak.
Guidance
- Users: keep your devices on the latest OS release so that any vendor fix for this class of issue is applied.
- Developers: only request Wi-Fi information through the documented, entitlement-gated APIs, request it only when genuinely needed, and treat any SSID you handle as location-grade personal data.
- Researchers: SSID-disclosure bugs are a recurring theme across platforms and devices; the permission surface around network identifiers is worth auditing on any system that claims to gate it.
Credit
Original research and proof-of-concept by speedyfriend433 (copyright Speedyfriend67, MIT License). Source repository: github.com/speedyfriend433/CVE-2026-84636-PoC.
Note: at the time of writing, the repository published the PoC source and license without a detailed advisory, so the version-specific affected range for this CVE was not confirmable from the source. The background above describes the vulnerability class and its context; specifics should be verified against the official CVE record once published.