Three days after iOS 27.2 shipped, the door Apple usually slams shut within days is still open. A fresh check of the signing tracker that follows Apple’s signing servers shows iOS 27.0.1 still signed on the morning of October 29, alongside iOS 27.1 for the iPhone Duo. For the small group of readers holding out for a jailbreak, that is a third day of borrowed time. For everyone else, a new government advisory is a reminder of what staying behind actually costs.
The October 29 signing check: still signed, on day three
The ONE Jailbreak signing status page, whose dated update is October 28 and which was re-crawled on the morning of October 29 at 08:23 UTC (13:53 IST), still lists iOS 27.0.1 among the versions Apple is signing, next to iOS 27.2, iOS 27.1, and iOS 26.7.2. That matches the check we reported yesterday, only the count has moved from two days to three.
The usual caveats still apply, and they matter more with each passing day. Signing is per device, not global, so a version listed as signed in general must still be signed for your exact model. And a signing page is a snapshot, not a promise. Apple has closed windows in the middle of a day before, with no announcement. The tracker’s own FAQ puts the typical window at 7 to 14 days after a new release, which means day three is not late, but it is also not early anymore.
What has not changed is the state of the jailbreak itself. Calif demonstrated an untethered jailbreak on iOS 27.0.1 in Paris on October 16, and jailbroke the iPhone Duo on its launch-day iOS 27.1 a week later. No tool exists for any iOS 27 version, and Calif has said it has no plans for an end-user tool, although a proof of concept may come later. The open window preserves a possibility. It does not create a jailbreak, and any site offering an iOS 27 jailbreak download today is selling something that does not exist.
CERT-In rated the iOS 27.2 flaws high severity on October 28
The new pressure on anyone still deciding comes from India’s Computer Emergency Response Team. CERT-In issued a high severity advisory on October 28, two days after Apple released the updates, warning that the flaws could let attackers run malicious code, gain privileges, steal data, or bypass security protections. The advisory covers not just iPhones but Macs, Safari, Apple Watch, Apple TV, and Vision Pro as well, according to reports from IBTimes India and Hans India.
That advisory does not change the technical facts of the jailbreak story, but it sharpens the trade. The bugs Calif used are part of the same patch: Apple’s iOS 27.2 notes list 163 CVE fixes for iPhone and iPad, including six credited to Calif, and researcher Stefan Esser has said most of the vulnerabilities behind the jailbreak demos are fixed in 27.2. Apple has said none of the iOS 27.2 flaws are known to be actively exploited. CERT-In’s rating is about severity, not about attacks in progress, and the two statements can both be true at once.
For most readers, the advice is unchanged and simple. Install iOS 27.2, as our report on its release explained, and keep Automatic Updates on. The update also unifies the iPhone Duo with other iPhones on the same version and brings new Siri AI languages on top of the security work. Devices that have not moved to iOS 27 get many of the same fixes in iOS 26.7.2.
Who should still wait, and what waiting now costs
The exception remains narrow. If a future jailbreak matters to you, staying on iOS 27.0.1, or iOS 27.1 on the Duo, preserves whatever chance the chain has left, and you can install 27.2 later. But CERT-In’s advisory puts a clearer price on that wait: every day on 27.0.1 is a day on a version with publicly documented flaws, including more than 30 WebKit fixes and about 15 kernel fixes, now rated high severity by a national CERT. That is a deliberate trade, not a default, and it only makes sense if you accept that no tool exists today and none has been promised.
One practical step costs nothing and does not require staying behind: save your SHSH2 blobs for iOS 27.0.1 while it is still signed. Blobs are Apple’s per-device signatures for a firmware version, and they can only be captured while the version is signed. Our blobs guide explains what they are and how to save them, and why a saved blob is the only way to keep a downgrade option alive after Apple stops signing. Saving blobs does not guarantee a future restore, but not saving them guarantees you will never have the option.
We will keep checking the signing status, and we will report the day it flips. Until then, the decision that could not wait on Monday still does not have to be rushed today, but the CERT-In advisory means it should no longer be postponed casually either.
