Possible new Cellebrite iPhone Radio Zero-Day

Justin.sh is reporting on a confidential Cellebrite document that has been leaked to him:

Cellebrite calls it Advanced Unlocks (AU from here on), not to be confused with the “advanced unlocking services” they’ve marketed for years. A press release from earlier this year confirms AU is a new product for 2026.

[…]

According to Cellebrite, AU:

  • is a “next-generation AFU vector that is more resilient to Apple’s OS changes”
  • works with Stolen Device Protection enabled, which tightens USB restrictions
  • is enabled by a dedicated appliance with a stated range (!) of about 8 meters.

AU = Advanced Unlocks, Cellebrite’s term. AFU = after first unlock.

Posted on October 20, 2026 at 7:03 AM • 3 Comments

Comments

Clive Robinson • October 20, 2026 11:47 AM

@ Brian Scott, Bruce, ALL,

You note,

<

blockquote>”… but Apple has it patched… ”

<

blockquote>

But what else do they not have patched?

The rate AI is finding not just bugs but exploitable vulnerabilities in peoples executable code, I would expect many serious vulnerabilities in Apple’s code.

Vulnerabilities that are “not known” to Apples Management and developers, so are,

“Zero days or earlier just waiting for discovery and exploitation.

Now ask yourself a question,

“If you had discovered a serious vulnerability in Apple Code, that you had developed a “Proof of concept exploit” code for…

What is it worth?

Some organisations are paying millions of dollars for iPhone Exploits.

What does Apple pay as a bug bounty…

Some years back now a battle cry of,

No more Free Bugs was the cry

And still senior managers and directors think that those doing “responsible disclosure” should have prosecutions pushed onto them…

One result as Microsoft found out is people develop a bitter hate and they repeatedly push “working exploit” code into the public arena to show how incompetent the senior decision makers are.

Jonathan • October 21, 2026 12:26 PM

From the article:

One fix stands out: a use-after-free (UAF) in the L2CAP channel manager.

Would using Rust or a language with a Rust like borrow checker have prevented this class of bug? It seems like the sort of thing Rust’s borrow checker was designed to prevent.

Leave a comment

Blog moderation policy

Login

Allowed HTML <a href="URL"> • <em> <cite> <i> • <strong> <b> • <sub> <sup> • <ul> <ol> <li> • <blockquote> <pre> Markdown Extra syntax via https://michelf.ca/projects/php-markdown/extra/

Sidebar photo of Bruce Schneier by Joe MacInnis.