| ▲ | outloudvi 3 hours ago | |
I won't call it NGINX2Root if it requires a vuln published a quarter ago (the SCTP one, probably CVE-2026-64564) to gain root. In this case it's an RCE, so... some NGINX2Shell? Also, Xint, if you are using SCTPhantom, you don't "discover" the SCTP vuln, you "reproduce" the SCTP vuln; Tencent discovered the SCTP vuln: https://matrix.tencent.com/en/2026/08/06/sctphantom-CVE-2026... The good thing is, Xint, thank you for doing responsible disclosure this time! I won't say https://copy.fail is responsible given the website was released before many distros have fixed the issue. Edit: So there's another unreleased SCTP vulnerability? Well, maybe it's time to turn it off if it's not used... > Does patching nginx close the whole chain? > It closes the way in through nginx. The kernel bug is a separate local privilege escalation vulnerability and needs its own patch, which will be released in the coming weeks. | ||