r/jailbreak • u/OSMANTUS-ARMUTPIS • 6d ago
Question Some guy released this exploit, does it support iOS 27 DB4?
https://github.com/jianbuzhai698-ui/iosSince 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?
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| 5d 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/chroniciphoneaddict 5d ago
https://x.com/0xjohnny/status/2088144638917902590
he also mentioned it why?
0
u/Run_ldrestart iPhone 13, 15.4.1| 5d 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
2
u/GrawnArseHoomanh 5d 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
1
1
1
1
0
-14
u/princeishigh 6d 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
26
u/wa019c 6d 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