Match the exact firmware to the exact project revision. This matrix records what the linked maintainers document. “Vulnerable,” “supported,” “tested” and “payload offsets exist” are different evidence levels. A numerical interval in a README can conceal missing individual releases, so the executable project's allowlist is especially important.
Reviewed 10 October 2026. Compatibility can change. Entries are documentary evidence, not a claim that this wiki tested every console or firmware.
Public chain and component matrix
| Project / component | Documented firmware | Meaning and qualification |
|---|---|---|
| Original IPv6 WebKit chain | 3.00, 3.10, 3.20, 3.21, 4.00, 4.02, 4.03, 4.50, 4.51 | Explicit original implementation list; loader historically uses 9020. |
| Original UMTX chain | Explicit versions below | Historical implementation; README warns its 5.00+ ELF loader does not work. |
| idlesauce UMTX2 | Maintainer states 1.00–5.50 | Updated host, PSFree entry and automatic Payload Dev loader. Do not transfer the old loader warning to this different implementation. |
| Relapse browser/kernel chain | Source allowlist below | README states 7.00–13.60; source omits 9.05 and 11.40. |
| Y2JB userland | At least 4.03; app/backup differs at 12.60 | Entry framework. Bundled Lapse is documented only through 10.01. |
| Relapse Y2JB port | Maintainer states 7.00–13.60 | Explicit reported test: 12.60, Y2JB 1.6, app 01.000.030. Requires working Y2JB. |
| BD-JB5 | Stock userland through 13.42 | 13.60+ instructions require an already jailbroken console and bdj_unpatch. |
| Poops Java kernel port | 12.00 or below | Requires an unpatched, working BD-J environment; this upper bound is not a verified list of every lower release. |
| P2JB Y2JB port | Maintainer states 9.00–12.40 | Separate slow kernel route. Do not extend this port's claim from another host's range. |
| Legacy kstuff 1.6.7 | Maintainer states 3.00–10.01 | Payload compatibility, requiring a compatible exploited environment. |
| kstuff-lite 1.11 Beta | Maintainer states 1.00–13.60 | Different payload branch. Release-wide support wording is not an exploit chain or feature-by-feature test matrix. |
The reviewed Relapse source revision is dd8e4e0 (30 September 2026); the Y2JB port revision is bcddec7 (1 October 2026).
Relapse's exact source allowlist
The firmware.js gate accepts these versions:
- 7.x: 7.00, 7.01, 7.20, 7.40, 7.60, 7.61.
- 8.x: 8.00, 8.20, 8.40, 8.60.
- 9.x: 9.00, 9.20, 9.40, 9.60.
- 10.x: 10.00, 10.01, 10.20, 10.40, 10.60.
- 11.x: 11.00, 11.20, 11.60.
- 12.x: 12.00, 12.02, 12.20, 12.40, 12.60, 12.70.
- 13.x: 13.00, 13.20, 13.40, 13.42, 13.60.
9.05 and 11.40 are not present. Removing a firmware check does not add offsets or repair an exploit. This list documents the current source gate, rather than independent confirmation of every payload on every listed release.
Original UMTX's explicit list
The historical PS5Dev README lists 1.00, 1.01, 1.02, 1.05, 1.10, 1.11, 1.12, 1.13, 1.14; 2.00, 2.20, 2.25, 2.26, 2.30, 2.50, 2.70; 3.00, 3.20; 4.00, 4.02, 4.03, 4.50, 4.51; and 5.00, 5.02, 5.10, 5.50. Its broader vulnerability discussion reaches 7.61, but its bundled WebKit entry was patched at 6.00. The supported implementation list therefore cannot be replaced with the vulnerability interval.
Payload and feature checks
The etaHEN release history identifies 2.5B as the current release; 2.4B specifically documents fixes for 8.40–10.01 and requires the Payload SDK ELF loader. That evidence does not establish universal etaHEN compatibility across Relapse's newer firmware list. Check the actual payload release and dependencies before loading it.
For low-firmware hypervisor research, Byepervisor describes the 1.x/2.x family while its included HEN is specifically documented for 2.50. A family-level vulnerability and a concrete HEN port remain separate rows of evidence.
How to update this matrix
Record repository owner, release tag or commit, date checked, exact console firmware, entry application revision, loader revision and successful capabilities. Label first-person maintainer tests separately from source inspection and issue comments. Preserve older rows when they explain guide incompatibility. Avoid filling gaps by interpolation, treating a screenshot as reproducible support, or assuming a future release will port missing versions. See research and source evaluation for a repeatable review method.