Researcher bypasses Ray-Ban Meta glasses firmware 127 signature check to run self-signed app
A security researcher, Paula Pamoutaf (pamoutaf), ran her own code on Ray-Ban Meta smart glasses by defeating the app-signature check that Meta added in firmware 127. Firmware up to and including 126 never verified that the Device Access Toolkit (DAT) APK was signed by Meta, so any app could be installed (p0pcycle.com). Firmware 127 enforced the check, but the on/off switch sits in a configuration file that the paired phone downloads from Meta's servers and forwards to the glasses, and the glasses only validated that the file was well formed (p0pcycle.com). Flipping one byte in that file disabled the check, and the researcher then reinstalled her self-signed app. The research needed control of the paired phone and did not show root access or a remote takeover of someone else's glasses (techtimes.co.uk). No CVE is assigned and no exploitation in the wild has been reported.
Entenda a falha
A vulnerabilidade
Ray-Ban Meta smart glasses firmware up to and including 126 never checked that the Device Access Toolkit (DAT) APK was signed by Meta, so any app could be installed. Firmware 127 added the check, but the switch that enables it, wss_appmanager.signature_verification_enabled, sits in a MobileConfig file that the paired phone downloads from Meta's servers and forwards to the glasses. The glasses only validate that the file is well formed, so changing one byte turns verification off. An attacker needs control of the paired phone, and gets their own self-signed app running on the glasses. No CVE has been assigned, and the articles do not name a fixed version.
Como funciona
The glasses are managed by the Meta AI app on the owner's phone. Developers add apps through a developer tool, and the phone sends the software to the glasses to install. The glasses get their configuration the same way: the phone fetches the MobileConfig file from Meta's servers and passes it over Airship. The glasses read the flag in that file to decide whether to verify the app's signature. They only confirm the file is well formed, not that it is untampered, so a modified flag is accepted and unsigned apps are installed and run.
Por que é vulnerável
In firmware 126 and earlier the cause was a missing check: no signature verification at all. In 127 the check exists, but the decision to enforce it is trusted to a configuration file relayed by the phone, which is not the glasses' own trusted state. The glasses validate only the file's format, not its authenticity or integrity, so whoever controls the phone can switch the protection off. The articles do not describe a fix.
Onde está
The flag is wss_appmanager.signature_verification_enabled in the MobileConfig file; the researcher changed its value in 0.mctable from 0x80 to 0x00.
Como foi descoberta
Security researcher Paula Pamoutaf (pamoutaf) found it while trying to run her own code on the glasses, and published a write-up on p0pcycle.com. She reported it through Meta's bug bounty program. She says she has not seen a public Meta advisory and assumes it is fixed because Meta approved her write-up. No CVE appears in her report, and no exploitation in the wild has been reported. She promised a follow-up on other ways to attack the glasses.
PoC pública
The researcher demonstrated a working chain: with the signature flag disabled, she reinstalled her self-signed app on the glasses. It exposed a shell reachable from the phone over a Wi-Fi Direct link on TCP port 31337, which lasted about five days before access was lost. The demonstration needed control of the paired phone and did not show root access or a remote takeover of someone else's glasses. The technical write-up is on p0pcycle.com; the articles do not mention released exploit code. The practical risk is low for ordinary users but real for anyone whose phone is compromised, so keep firmware and the Meta AI app updated.
Explicação gerada por IA a partir da matéria e dos artigos, em 10/11/2026 13:30.
Detalhes técnicos
- The glasses fetch their configuration through the phone, which retrieves it from Meta's servers and passes it over Airship; the flag controlling app-signature verification is
wss_appmanager.signature_verification_enabledin the MobileConfig file (p0pcycle.com). - The researcher changed the value in
0.mctablefrom 0x80 to 0x00 to disable verification (p0pcycle.com). - Her app ran on the glasses with a shell reachable from the phone over a Wi-Fi Direct link on TCP port 31337, and the shell lasted about five days before access was lost (p0pcycle.com, techtimes.co.uk).
- The glasses have no screen, so debugging relied on audio beeps (p0pcycle.com).
- The researcher reported the issue through Meta's bug bounty program and says she has not seen a public Meta advisory; she assumes the issue is fixed because Meta approved her write-up (p0pcycle.com). No CVE identifier appears in her report (it-connect.tech).
Remediação
- Update the glasses through the Meta AI app to the latest firmware, and keep the Meta AI app itself current.
- Install only apps from official sources and avoid modified or unofficial software on the glasses.
- Protect the paired phone, since the published chain depended on the phone to deliver the configuration and to hook the Meta AI app.
Linha do tempo
-
Researcher bypasses Ray-Ban Meta glasses firmware 127 signature check to run self-signed app
ler a análise desta fonte ocultar
A security researcher, Paula Pamoutaf (pamoutaf), ran her own code on Ray-Ban Meta smart glasses by defeating the app-signature check that Meta added in firmware 127. Firmware up to and including 126 never verified that the Device Access Toolkit (DAT) APK was signed by Meta, so any app could be installed (p0pcycle.com). Firmware 127 enforced the check, but the on/off switch sits in a configuration file that the paired phone downloads from Meta's servers and forwards to the glasses, and the glasses only validated that the file was well formed (p0pcycle.com). Flipping one byte in that file disabled the check, and the researcher then reinstalled her self-signed app. The research needed control of the paired phone and did not show root access or a remote takeover of someone else's glasses (techtimes.co.uk). No CVE is assigned and no exploitation in the wild has been reported.
Technical Details
- The glasses fetch their configuration through the phone, which retrieves it from Meta's servers and passes it over Airship; the flag controlling app-signature verification is
wss_appmanager.signature_verification_enabledin the MobileConfig file (p0pcycle.com). - The researcher changed the value in
0.mctablefrom 0x80 to 0x00 to disable verification (p0pcycle.com). - Her app ran on the glasses with a shell reachable from the phone over a Wi-Fi Direct link on TCP port 31337, and the shell lasted about five days before access was lost (p0pcycle.com, techtimes.co.uk).
- The glasses have no screen, so debugging relied on audio beeps (p0pcycle.com).
- The researcher reported the issue through Meta's bug bounty program and says she has not seen a public Meta advisory; she assumes the issue is fixed because Meta approved her write-up (p0pcycle.com). No CVE identifier appears in her report (it-connect.tech).
Remediation
- Update the glasses through the Meta AI app to the latest firmware, and keep the Meta AI app itself current.
- Install only apps from official sources and avoid modified or unofficial software on the glasses.
- Protect the paired phone, since the published chain depended on the phone to deliver the configuration and to hook the Meta AI app.
- The glasses fetch their configuration through the phone, which retrieves it from Meta's servers and passes it over Airship; the flag controlling app-signature verification is