
Mining KRW at @theori_io in @dreamhack_io, @xint_official team; playing CTF with The Duck, MMM
Joined September 2016
- Tweets501
- Following314
- Followers1.2K
- Likes762
bincat retweeted
Replying to @lcamtuf
This is largely true, but note that Xint found 5 bugs. 3 of which weren't discovered by anyone else
I'm happy to introduce our team's work 😎 check: nginx2root.com
🚨 Critical nginx vulnerabilities disclosed. Immediate action recommended.
If you run nginx, check whether your servers are affected and update to the patched version immediately. If you cannot upgrade, follow the mitigation guidance at nginx2root.com
Today we’re disclosing nginx2root, five distinct vulnerabilities in one of the world’s most widely deployed web servers, each capable of unauthenticated remote code execution under affected conditions. One of these vulnerabilities affects nginx’s most common configuration. We’ve also demonstrated a fully remote, unauthenticated exploit chain that escalates from nginx RCE to root access on the underlying server, using a separate Linux kernel vulnerability.
Why this is so important:
One of these bugs has been hiding in nginx’s HTTP/2 implementation since 2015. That’s more than a decade in software that powers roughly a third of the web. Every official release from 1.9.5 through 1.31.8 contains the vulnerable code, including the master branch as of Nov 10, 2026.
A Xint researcher found the specific vuln that hits nginx in its default config. This discovery was around the same time he found another critical vulnerability in a different project that we cannot talk about yet due to the same concerns as nginx2root. We took those learnings and incorporated them into the harness as a new, general Xint feature (that is, not fine-tuned to nginx), which then found the other 4 critical nginx vulnerabilities with no human guidance.
We coordinated disclosure with the nginx maintainers and major cloud providers to help make fixes available before publication.
Technical details, affected versions, and remediation guidance:
nginx2root.com
bincat retweeted
nginx2root.com
Multiple critical bugs in nginx affecting common configurations, each one indepedently exploitable for unauthenticated RCE.
For demo purposes, it is chained with a Linux LPE and container escape.
Patch!!
Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens.
Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root.
One of themhits the default config.
If you run nginx, patch now. Then read: nginx2root.com
CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425
bincat retweeted
🚨 Critical nginx vulnerabilities disclosed. Immediate action recommended.
If you run nginx, check whether your servers are affected and update to the patched version immediately. If you cannot upgrade, follow the mitigation guidance at nginx2root.com
Today we’re disclosing nginx2root, five distinct vulnerabilities in one of the world’s most widely deployed web servers, each capable of unauthenticated remote code execution under affected conditions. One of these vulnerabilities affects nginx’s most common configuration. We’ve also demonstrated a fully remote, unauthenticated exploit chain that escalates from nginx RCE to root access on the underlying server, using a separate Linux kernel vulnerability.
Why this is so important:
One of these bugs has been hiding in nginx’s HTTP/2 implementation since 2015. That’s more than a decade in software that powers roughly a third of the web. Every official release from 1.9.5 through 1.31.8 contains the vulnerable code, including the master branch as of Nov 10, 2026.
A Xint researcher found the specific vuln that hits nginx in its default config. This discovery was around the same time he found another critical vulnerability in a different project that we cannot talk about yet due to the same concerns as nginx2root. We took those learnings and incorporated them into the harness as a new, general Xint feature (that is, not fine-tuned to nginx), which then found the other 4 critical nginx vulnerabilities with no human guidance.
We coordinated disclosure with the nginx maintainers and major cloud providers to help make fixes available before publication.
Technical details, affected versions, and remediation guidance:
nginx2root.com
bincat retweeted
Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens.
Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root.
One of themhits the default config.
If you run nginx, patch now. Then read: nginx2root.com
CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425
bincat retweeted
🚨🚨 Xint researcher @tjbecker found a vulnerability that enabled large scale OpenAI model reasoning distillation that bypassed earlier mitigations set in place post-Stolen Thoughts. We disclosed responsibly to OpenAI and they completed patching last week. Full technical writeup here.
xint.io/blog/compaction-smug…
bincat retweeted
**Kia's success with Xint**
Product security teams were already short staffed even before AI expanded the attack surface. KIA’s Red Team was looking to not just find more bugs, but to accelerate remediating important vulnerabilities.
Kia’s Red Team brought in Xint to take on the repetitive, time-consuming parts of security testing. Xint finds vulnerabilities and delivers validated findings with clear remediation guidance, so the team spends less time chasing false positives and more time getting real issues fixed. With Xint, the same single tester can now cover more ground on every project.
With Xint, Kia’s Red Team has increased bug discovery by 33%, bug triage by 17%, and bug remediation by 50% in an average month, all without increasing headcount! Overall, the team now handles roughly 30–40% more vulnerabilities per month than before.
bincat retweeted
Any Android app on a Pixel can turn the phone off. It took three hours to find, and we never even saw the source code.
xint.io/blog/android-app-shu…
bincat retweeted
Xint has been recognized as an
@IDC Innovator for Autonomous Penetration Testing for DevSecOps in 2026. From the IDC Research Director Katie Norton: "Many high-impact application vulnerabilities emerge from valid actions performed in the wrong order, by the wrong role, or under the wrong state. Xint's focus on workflow sequence, state, roles, and business logic helps move testing beyond endpoint coverage and toward abuse path validation. For security teams, this creates a better fit for finding issues, such as authorization gaps, privilege escalation paths, and multistep business logic flaws, that conventional dynamic testing can miss."
bincat retweeted
Xint researcher @junorouse talks to @letsdatascience about how to hack (and protect) AI apps:
"If you ship a compiled binary, scanners are getting good enough at pulling it apart to read it anyway. If you ship a web service and no code at all, they'll find bugs by probing it from the outside...you should be designing on the assumption that your source code leaks at some point, not on the hope that it doesn't."
letsdatascience.com/news/the…
bincat retweeted
Hey everyone. We’ve seen the discussions around Copy Fail (CVE-2026-31431) and the disclosure process. We appreciate the passion from distro maintainers, defenders, and the broader Linux community. This is a serious issue, and we want to share some context on our side in good faith. 🧵
bincat retweeted
So an AI just broke Linux and the story is actually insane:
• theori is a 9-time DEF CON CTF champion security firm, the kind of people who hack competitions for fun and win every time
• they point their AI system, Xint Code, at the linux kernel's crypto subsystem like it's a saturday puzzle
• one operator prompt. one hour. no custom tooling. no harnessing. nothing.
• the AI finds a bug that has been sitting quietly in every linux distribution since 2017
• ubuntu, amazon linux, rhel, suse, debian, arch, fedora. all of them. nine years of kernel security review. missed.
• the exploit is a 732-byte python script. no race window to win, no per-kernel offset to calculate, no luck required
• same script. every distro. root shell. every single time.
• crypto reviewers missed it for nine years because they were looking for cryptography failures. this wasn't one. it was a memory question. different discipline entirely. the AI didn't care.
• oh and it's also a container escape. one pod in a kubernetes cluster runs this script and owns the entire host and every tenant on it
• zerodium used to pay up to $500,000 for exactly this class of vulnerability
bincat retweeted
Patch your Linux boxes!
Copy.Fail is a trivially exploitable logic bug in Linux, reachable on all major distros released in the last 9 years. A small, portable python script gets root on all platforms.
Found by the teams at @theori_io and @xint_official
More details below
xint.io/blog/copy-fail-linux…
bincat retweeted
‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP.
The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years.
Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box.
The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root.
Result: the next time anyone runs that program, it lets the attacker in as root.
What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk.
Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants.
The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today.
This vulnerability affects the following:
🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root
🔴 Kubernetes and container clusters: one compromised pod escapes to the host
🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner
🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root
Timeline:
🔴 March 23, 2026: reported to the Linux kernel security team
🔴 April 1: patch committed to mainline (commit a664bf3d603d)
🔴 April 22: CVE assigned
🔴 April 29: public disclosure
Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module:
echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
rmmod algif_aead 2>/dev/null || true
For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...























