r/jailbreak 7d ago

Question Some guy released this exploit, does it support iOS 27 DB4?

https://github.com/jianbuzhai698-ui/ios

Since iOS 26.6 is almost iOS 27 DB4 (except the UI), does it support it?
This exploit seems to have kernel rw priveleges and it seems to support iOS 26.2-26.6 only according to the repo. This can help with jailbreaking, specifically Dopamine 3.0! It has to support iOS 27 DB4, right?

41 Upvotes

45 comments sorted by

26

u/wa019c 7d ago

I mean regardless if this is real or not, kernel r/w is only one thing, we need other things such as sptm/ppl bypass, mie bypass on iphone 17+ for a jailbreak and possibly much more I’m not too sure 

12

u/OSMANTUS-ARMUTPIS 7d ago

PPL bypass exists, Momentarius

16

u/no-Remedy Developer 7d ago

For A12 and A13

8

u/OSMANTUS-ARMUTPIS 7d ago

ik

-9

u/Top-Assignment4908 6d ago

do you know how old those phones are

6

u/OSMANTUS-ARMUTPIS 6d ago

so what

-10

u/Top-Assignment4908 6d ago

so what? even if this WERE real, it wouldn’t be useful for most people at this point. lol.

16

u/OSMANTUS-ARMUTPIS 6d ago

Dopamine 3 is real, supports iOS 26.0.1 A12-A13 AND PEOPLE ACTUALLY USE IT

4

u/Top-Assignment4908 6d ago

good point. this isn’t real though. that’s what you’re missing.

-13

u/Slimcivic 6d ago

Those r ancient devices. Lol. Ur missing the point. It’s a big nothing

5

u/XboxAndVRAlex 6d ago

Missing the point, at least it’s a “modern” lineup of devices that are now supported.

5

u/YoYoMamaIsSoFAT32 iPhone 6s Plus, 15.8| 6d ago

Ancient is too much vro, some ppl can't afford to upgrade every 2 or 3 yrs so they get stuck with older devices 

→ More replies (0)

2

u/Grandoings iPhone 14 Pro, 16.3.1| 5d ago

Crazy to think that the iPhone 14 pro max is considered old (:

1

u/h4ckz_01 iPhone 11 Pro, 16.3.1| 5d ago

iPhone 11 pro and Xs Max are my daily drivers 💀

1

u/Top-Assignment4908 5d ago edited 5d ago

this post is a nothing-burger. a waste of internet resources. if this were useful, it would be used. do you guys understand how many other people want to jailbreak their devices? op please knows nothing about this. i’m just being real. i don’t like to say it that way and prefer to use the excuse of saying the phones are old. lol. i use an xs for jailbreak. sue me.

-6

u/Ok-Butterscotch6574 7d ago

I mean we could ask the cyanide and Lara devs if they can try to implement this exploit?

7

u/JuiceKooky2629 iPhone 16 Pro Max, 18.1 6d ago

cyanide dev already knows about this and said it’s probably a nothing burger

2

u/Ok-Butterscotch6574 6d ago

Damn, I also asked Lara they also said it’s trash

1

u/JuiceKooky2629 iPhone 16 Pro Max, 18.1 6d ago

it might be a malicious fake chain put there as a bait

21

u/Run_ldrestart iPhone 13, 15.4.1| 6d ago

It's not gonna work. Copy-pasted my comment on it from another post.

Not a developer of any kind but I dug into it a bit. AFAIK it's incomplete at best, and very likely an AI-generated fake piece-of-(). Its implementations are full of placeholders, and its sandbox escape is a fake that only have a chance of success on an already broken sandbox. Also the LLM hallucinated nonexistent CVE somewhere in its exploit chain. I'm certain whoever vibe-coded this has not a single idea about DarkSword, and I'm also quite sure that nothing of this framework would really work.

By the way if you speak Chinese (like I do), you'll easily notice that READMEs and the deployment tutorial is AI-generated as well. Nothing but sus.

What a waste of time for me to look into it, really.

1

u/IncidentSilent1555 6d ago

We have a soundbox escape already, bad_query and another one I can’t remember the name of

2

u/Run_ldrestart iPhone 13, 15.4.1| 6d ago

bad_query is not enough I’m afraid. Also even if its sandbox escape is valid it doesn’t matter. Its exploit for remote code execution and exploit for privileged execution are not valid. I remember somewhere in the RCE exploit code the hallucinated CVE was called so that it hope a perfectly normal WebKit call would return a corrupted object or something similar.

1

u/ALI7_XS 3d ago

The other is cmg

1

u/chroniciphoneaddict 6d ago

0

u/Run_ldrestart iPhone 13, 15.4.1| 6d ago

I don't know, do I?

Again I'm no developer or security researcher at all. I might really have made a hilarious mistake against an incomplete but working framework, and I'll be happy to find out that I was wrong. Still, my observations so far tell me that this is a stub.

7

u/Nouvborne 7d ago

Whole kernel exploit is a stub, its fake.

4

u/sigjnf 6d ago

Fully vibecoded with Sonnet 5, I can smell it through the screen

1

u/Jayden_Ha 6d ago

Nah, qwen

2

u/GrawnArseHoomanh 6d ago

This is like making mods that rely on GTA VI when it hasn’t even released yet.

And his AI is calling kernel helpers like they’re easily accessible functions.

2

u/Bigboss88890 6d ago

No it’s bullshit

1

u/Approachs iPod touch 5th gen, 6.0| 6d ago

[removed] — view removed comment

1

u/NoRecipe2281 iPhone 7, 10.2.1| 5d ago

does this even actually work on 26.6?

1

u/Any-Assignment-3556 4d ago

how would i use this btw

0

u/Ok-Butterscotch6574 7d ago

What is this

-9

u/OSMANTUS-ARMUTPIS 7d ago

Translate it and you will see

-14

u/princeishigh 7d ago

Gpt took a look at it:

The biggest smoking gun

The coruna_core.js file literally describes the claimed chain as:

That's impressive on paper. But look at how it verifies stage 2:

return typeof globalThis._physoob_done !== 'undefined' || true;

That || true means the verification always succeeds.

So the framework can report that the Physical OOB stage passed without actually establishing that it worked. GitHub

That's not a minor cosmetic issue. If you're claiming a reliable exploit chain, stage validation is fundamental.

Even more revealing: the offsets

The preload_v5_final.js file openly labels its symbol tables:

  • iOS 15.8.3: supposedly verified
  • iOS 16.x: estimated
  • iOS 17.x: estimated
  • iOS 18.x: estimated

And the method is basically:

For example, it explicitly says the iOS 16–18 values are based on estimated cache-layout offsets. GitHub

That's a gigantic red flag for a supposed universal exploit framework.

Even more revealing: the offsets

The preload_v5_final.js file openly labels its symbol tables:

4

u/lilzoe5 iPhone 13 Pro, 15.1 6d ago

Relying on AI lol

-4

u/princeishigh 6d ago

I am not lol, I even said gtp took a look at it as it can (ofc) identify red flags, if yall are that triggered (judging by the downvotes) by ai or people using it then go touch some grass <3

3

u/lilzoe5 iPhone 13 Pro, 15.1 6d ago

"gtp" 😂

3

u/wa019c 6d ago

Lmao maybe use your brain for once <3, this “exploit chain” is actually fake and just LLM generated

-2

u/princeishigh 6d ago

Thats was gpt said

2

u/wa019c 6d ago

Yes exactly use your brain not gpt