← Voltar ao feed

OffensiveCon Japan 2026 previews Chrome Skia sandbox escape, Telegram sticker zero-click and iOS zero-day research

1 fonte(s) · 1 atualização(ões) · publicado 29/10/2026 03:00 · coletado há 3 dias

OffensiveCon Japan 2026 ran on October 27–28 and featured research on Chrome renderer sandbox escapes, Telegram zero-click attack surfaces and iOS zero-day discovery. The article stresses that session titles do not establish working exploit chains, affected versions or active exploitation. No advisory, CVE assignment, indicators or patch information accompanies the agenda.

Quang L's talk targets escaping the Chrome renderer sandbox via Skia, and Saifeldeen Aziz's talk covers Telegram vulnerabilities and bypasses around stickers. Luke McLaren's talk covers discovering iOS 0-days with "Muse Spark". Other sessions covered V8 security in the age of AI, Apple virtualization guest-to-host attacks, MediaTek GenieZone, GPU drivers, NTFS, Linux io_uring, Safari exploits and WMI devices.

Exploit público

Há código de exploração publicado no Exploit-DB para CVE-2025-2783. O código não é reproduzido aqui: o link leva à fonte, e a explicação foi escrita pela IA a partir do arquivo publicado.

  1. exploit-db.com · EDB-52403 ↗ · aplicação web · windows · pub. 11/08/2025 não verificado

    Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape

    This file does not really exploit CVE-2025-2783. It is a Python script that only simulates a Mojo IPC sandbox escape: a small local web server serves a JSON file, and a client fetches it and passes it over Python's own inter-process channel, logging user and system details. It never touches Edge or Chromium code, so it achieves no real escape or privilege gain. Its reference cites a different CVE (CVE-2025-49730). Treat it as a mock demo, not a working exploit.

    CVE-2025-2783 · autor: nu11secur1ty · explicação gerada por IA

Detalhes técnicos

  • The Skia talk does not disclose the underlying flaw, prerequisites, or whether a prior browser bug was needed.
  • CVE-2025-2783 (Windows handle processing and Chrome IPC) is cited only as historical context. It is not linked to the Skia research.
  • The Telegram listing names no affected clients, CVEs or confirmed full zero-click compromise.
  • The iOS listing gives no vulnerability identifiers or patch details, so it should not be read as confirming an unpatched exploit.

Remediação

No remediation is provided. Defenders should treat these items as research topics and watch for vendor advisories from Google, Telegram and Apple.

Linha do tempo

  1. gbhackers.com ↗ · pub. 29/10/2026 03:00 · coletado 29/10 05:00 primeiro registro

    OffensiveCon Japan 2026 previews Chrome Skia sandbox escape, Telegram sticker zero-click and iOS zero-day research

    ler a análise desta fonte

    OffensiveCon Japan 2026 ran on October 27–28 and featured research on Chrome renderer sandbox escapes, Telegram zero-click attack surfaces and iOS zero-day discovery. The article stresses that session titles do not establish working exploit chains, affected versions or active exploitation. No advisory, CVE assignment, indicators or patch information accompanies the agenda.

    Quang L's talk targets escaping the Chrome renderer sandbox via Skia, and Saifeldeen Aziz's talk covers Telegram vulnerabilities and bypasses around stickers. Luke McLaren's talk covers discovering iOS 0-days with "Muse Spark". Other sessions covered V8 security in the age of AI, Apple virtualization guest-to-host attacks, MediaTek GenieZone, GPU drivers, NTFS, Linux io_uring, Safari exploits and WMI devices.

    Technical Details

    • The Skia talk does not disclose the underlying flaw, prerequisites, or whether a prior browser bug was needed.
    • CVE-2025-2783 (Windows handle processing and Chrome IPC) is cited only as historical context. It is not linked to the Skia research.
    • The Telegram listing names no affected clients, CVEs or confirmed full zero-click compromise.
    • The iOS listing gives no vulnerability identifiers or patch details, so it should not be read as confirming an unpatched exploit.

    Remediation

    No remediation is provided. Defenders should treat these items as research topics and watch for vendor advisories from Google, Telegram and Apple.