NewsSANS NewsBites
Apple Fixes Flaw in Hide My Email Feature that Exposed Addresses
NEOSEC enrichment — no mirror of the original source
Over a year after it was first reported, Apple has fixed an issue that exposed the real email addresses of users using the Hide My Email feature. This privacy feature allows users to create temporary anonymized email aliases using the iclou
Source: SANS NewsBites. For licensing reasons NEOSEC Intel does not mirror the full text verbatim. The full text and expert commentary are available at the original source.
Editorial context in the original issue
The SANS NewsBites issue carries commentary by: Dukes, Neely, Skoudis, Ullrich.
More on Addresses
Other advisories
- Not ratedosv:CVE-2026-118376WeKnora before 0.8.2 SSRF Guard Bypass via NAT64 IPv6 Addresses
- Not ratedosv:CVE-2026-99092riscv: patch: fix handling of bpf-jit execmem addresses
- CriticalCVE-2026-106072A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
- CriticalCVE-2026-105483A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.
- Not ratedosv:CLEANSTART-2026-PU19584ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-AO39613ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-XD91859ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-WB16925ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
Other news entries
- "Icepick" leak exposes records on 41,000 DHS employees, including undercover ICE agentsBreachpwn.watch
- zkLink Nova's Ethereum bridge drained of about $786K through a forged batch rootBreachpwn.watch
- PHP2Shell Exploitation Moves From Probes to Working ShellsNewsSecurityWeek
- 11 Million Impacted by Capcom Data BreachNewsSecurityWeek
- Capcom confirms data breach affecting 11.7 million accountsNewsBleepingComputer
- CoinDCX loses 15.99M USDT from a retired TRON wallet compromised in its 2025 hackBreachpwn.watch
- Hackers Steal 1.8 Million Records From NikkeiNewsSecurityWeek
- University of Copenhagen breach exposes data of 525,000 peopleBreachpwn.watch
ID