mrkeyoor.comAsk

0xjohnnydev/airlifttested 03 Oct 2026commit c684cd4

airlift review

Use Airlift for a specific AirTraffic boundary investigation when you can verify the canary and cleanup on paired hardware.

  • Build 6 s
15 sto install
  • 35 packages
Dev Toolsevaluationupdated 31 Oct 2026
+2stars / 7d

Choose Airlift to investigate a paired iPhone's AirTraffic file boundary, with hardware available to verify the result. Airlift makes one new file outside AirTraffic's intended Media area. It reads that canary back and removes it; this is a media-service boundary escape, not kernel access or control of the whole phone. Our run on October 3, 2026, used commit c684cd4. It recorded successful install and build steps in our Debian sandbox, but did not validate the escape on an iPhone.

Verdict

Use Airlift for a specific AirTraffic boundary investigation when you can verify the canary and cleanup on paired hardware. Our October 3, 2026 run at c684cd4 recorded installation in 15 seconds and a successful build step in 6 seconds, with 29 seconds recorded overall; tests were skipped. It did not validate the exploit. The current README documents a narrower fixed-destination demonstration on 24A437 than its historical directory list, so choose the checkout first and verify its stated behavior on the intended device.

We ran it

Lab card: what happened when we ran airlift
Lab card from our sandbox run
Screenshot of airlift (github.com/0xjohnnydev/airlift)
github.com/0xjohnnydev/airlift
Install✓ · 15s35 packages · 37 MB
Build✓ · 6s
Testsn/ano test script
Known vulns0(pip-audit)
Repo9 files~548 lines of source · 0.2 MB · 0 CI workflows

Answers from our run

Does airlift build from source?

Dependencies installed in 15 seconds (35 packages), and the build succeeded in 6 seconds. We cloned commit c684cd4 into a clean Debian container with 3 CPUs and no project-specific setup.

Does airlift have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does airlift have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use airlift?

Readers seeking a jailbreak, kernel access, or general control of an iPhone.

What are the alternatives to airlift?

libimobiledevice, pymobiledevice3. Use Airlift for a specific AirTraffic boundary investigation when you can verify the canary and cleanup on paired hardware.

Setup2/5Substantial setup constraints: the documented device workflow requires a Mac, Xcode, and a trusted paired iPhone; our Debian command outcomes do not validate that workflow.
Docs4/5Detailed documentation explains scope, prerequisites, byte recovery, and cleanup. Readers must distinguish the current fixed-destination workflow from the measured commit.
Community2/5Limited supporting evidence: a detailed external issue documents one environment, but the supplied extracts do not establish adoption, maintainer responsiveness, or support quality.
Maturity1/5Research-artifact rating: the measured checkout had no detected tests or CI, and our sandbox did not validate device behavior or the current cleanroom implementation.

Who it’s for

iOS security researchers investigating the AirTraffic and Books sync file boundary.
Apple-platform developers who can reproduce the documented workflow on a Mac and a paired test iPhone.
Researchers who will check exact-byte recovery and cleanup rather than treating returned API calls as proof of a write.

Who it’s NOT for

Readers seeking a jailbreak, kernel access, or general control of an iPhone.
Anyone treating our Linux sandbox result as verification of the native Mac helpers or device behavior.
Researchers assuming the current fixed /var/tmp demonstration verifies every historically reported destination on build 24A437.
Anyone who needs a dependable device workflow without first checking the exact host, phone, and iOS build.

Setup reality

Our run on October 3, 2026, used commit c684cd4 in a Python 3.12 Debian Bookworm sandbox with 3 CPUs and 8 GB RAM. The stored harness reports installation in 15 seconds, 35 packages occupying 37 MB, and a successful build step in 6 seconds. Its recorded total elapsed time is 29 seconds. Tests were skipped because no script was detected.

The harness records each command step's outcome, exit code, elapsed time, and available log tail. Install and build both returned exit code 0. The build tail is empty, so the record does not identify a compiler invocation or establish that the native helpers compiled. We did not test pairing, AirTraffic calls, a canary write, readback, or cleanup on a phone.

The current README requires a Mac with Python 3 and Xcode, plus a paired iPhone that trusts the Mac and is connected by USB. It documents a different entry point and a fixed destination compared with the README at our measured commit. Follow the instructions belonging to the checkout you intend to test.

What our sandbox result establishes

Our run on October 3, 2026, used commit c684cd4. The attached harness record reports a successful 15-second installation and a successful 6-second build step in our Debian sandbox. The recorded total is 29 seconds; adding the two step durations does not describe the whole run.

Tests were skipped because the harness detected no test script. A skipped test step is not a failed suite, and there are no passing-test counts to report. The build command returned zero, but its stored log tail is empty. That outcome does not establish that the Mac helpers compiled or that the device workflow ran.

The checkout contained 9 files and about 548 lines of source, occupying 0.2 MB. The record detected no CI workflows or tests directory. Pip-audit recorded 0 advisories, with packages recorded as 0 and no scannedPackages field. Scan coverage is unknown; the result does not establish that all 35 installed packages were scanned or that Airlift is secure.

The MrKeyoor testing methodology explains command outcomes and sandbox limits. That page provides provenance context, not evidence that its current procedure was used for this older run. This correction uses the stored record and includes no new execution.

What the current demonstration proves, according to its README

Airlift makes one new file outside AirTraffic's intended Media area. The current README describes a randomly named canary at a fixed /var/tmp destination on iOS 27.0 build 24A437, used on an iPhone 18 Pro. It moves the canary back into Media, reads it through AFC, and compares the recovered bytes.

The README explicitly limits the meaning of sandbox escape: the media service crosses its intended file boundary. It does not claim kernel access or control of the whole phone. Its destination list concerns fresh files, not overwriting existing ones, and a working path to the MobileGestalt plist has not been shown.

For interpreting a device result, exactBytesRecovered means the recovered bytes match the canary, while cleanupComplete means the temporary files were removed. The README says a successful run reports both as true. Returned AirTraffic API calls alone do not confirm delivery; file readback supplies evidence of the effect. If cleanup cannot finish, the documented result identifies a recoveryFiles directory on the Mac.

These are upstream descriptions of the current demonstration. Our sandbox did not verify them on hardware.

Keep the measured commit separate from current instructions

The README at our measured commit reported testing on iOS 27.0 RC build 24A435 and said final build 24A437 should also work. It described an interactive device selection flow and a configurable destination.

The current README instead documents cleanroom/poc.py, accepts build 24A437, and fixes the demonstration destination to /var/tmp. It attributes the other listed directory results to 24A435 and explicitly says this PoC does not exercise those directories on 24A437. Those current instructions and claims must not be presented as behavior tested by our October run.

Issue 4 reports a staging failure on 24A437 using the older commit c684cd41ca0ded2d1ab780c15f6ead05509ce062. Its author reports kAMDInvalidCheckinError and attributes the failure to an entitlement requirement. That is a reported failure in a specified environment. It neither proves that every 24A437 setup fails nor independently verifies the current cleanroom demonstration.

Before reproducing the result, record the checkout, Mac environment, iPhone model, and iOS build. Use that checkout's documentation, then inspect byte recovery and cleanup. Our successful sandbox command outcomes cannot substitute for those device checks.

Choose a device toolkit when the exploit is not your question

libimobiledevice is a cross-platform library for communicating with iOS device services without existing proprietary libraries. Its documented utilities cover tasks such as pairing, backups, diagnostics, and AFC access. Choose it for ordinary device-service integration; its documentation does not establish reproduction of Airlift's boundary escape.

pymobiledevice3 provides a Python API and command-line tool for interacting with iOS devices on Windows, Linux, and macOS. Choose it when Python automation and its documented device services answer your task. Either toolkit can complement a research workflow, but neither supplied source establishes it as a replacement implementation of this exploit.

How to read the retained ratings

These editorial scores use a five-point rubric: 1 indicates a research artifact with substantial validation gaps; 2 indicates substantial constraints or limited supporting evidence; 3 indicates adequate evidence for the stated use; 4 indicates clear, detailed support with remaining limits; 5 requires broad corroboration across the dimension. They are judgments, not measured performance or adoption.

Setup ease remains 2 because the meaningful workflow needs a Mac, Xcode, and paired hardware beyond our sandbox. Documentation remains 4 because the supplied README explains the boundary, prerequisites, result flags, and cleanup, while historical and current instructions require care. Community remains 2: the supplied issue provides a detailed external report, but the evidence does not establish response quality or adoption. Maturity remains 1 because our measured checkout had no detected tests or CI, and we have no independent device validation of the current demonstration.

Alternatives

ProjectWhat it isPick it when
libimobiledeviceA cross-platform library and utilities for communicating with iOS device services without existing proprietary libraries.Choose it for device-service integration, pairing, backups, diagnostics, or AFC access. It can complement research, but the supplied source does not establish reproduction of Airlift's escape.
pymobiledevice3A Python API and command-line tool for interacting with iOS devices on Windows, Linux, and macOS.Choose it for Python automation of its documented device services. It can complement an investigation; it is not established here as an implementation of Airlift's exploit.

What people are saying

  1. [velocity-scout] 0xjohnnydev/airlift

Sources

  1. Airlift README
  2. Airlift Makefile
  3. Issue 4: iOS 27 entitlement-gate report
  4. Pull request 3: Windows canary host

More dev tools reviews