On November 4, 2026, OpenAI published research describing an AI-based system that developed working exploits for 948 distinct vulnerabilities in the Linux kernel that allowed privilege escalation. According to the company, those exploits let an ordinary user gain root privileges in its tests — the highest administrative privileges on the system. The researchers also produced proposed fixes for the findings. OpenAI’s research.
That needs some context: local privilege escalation assumes the attacker can already run code on the machine with limited permissions. The experiment does not mean that anyone can now take over any Linux computer with a single request over the internet. It does show how dangerous an initial foothold can become, even when that foothold was supposed to have limited reach.
The research system read code, tested suspected bugs in isolated virtual machines, developed exploits and proposed patches. Specialists then reviewed the results. The full run cost around $1.2 million in API credits. That is the cost of using the models, rather than the complete research budget including people and infrastructure. Methods and costs.
This changes the economics of vulnerability research. Work can be spread across many agents: one examines a piece of code, another tests a finding, and a third tries to establish its impact. Human expertise is still needed, but researchers can pursue many more investigations at the same time.
The speed of moving from a discovered bug to practical exploitation is especially worrying. A security patch itself gives researchers clues about where the problem was. In a separate academic study, a system called K-Repro used Linux kernel patches to automatically produce programs that reproduced bugs in more than half of a sample of 100 vulnerabilities. A reproducer is not yet a reliable exploit, but it removes part of the work required. The Patch-to-PoC study.
For a server owner, this means a tighter race against the clock. Developers may already have released a fix while the administrator is still planning a weekend update. If an attacker can analyse the change and prepare an exploitation tool sooner, that gap becomes particularly dangerous. The UK’s National Cyber Security Centre explicitly expects AI to shorten the time between vulnerability disclosure and exploitation. The NCSC assessment.
These findings do not justify writing off Linux or assuming that another operating system is automatically safe. A large number of discovered bugs also reflects the capabilities of the tools now being used to examine complex code. Security has specific conditions and boundaries: the software version, configuration, enabled features, user permissions and hardware. Even the Linux kernel’s official threat model describes its protections in terms of such assumptions. The Linux kernel threat model.
No complex system should be treated as guaranteed to be invulnerable. A developer’s reputation, open or closed source code, and years of use cannot provide that guarantee. New tools can uncover weaknesses that earlier reviews missed.
The risk becomes particularly serious when the adversary is a well-funded state organisation. Such a team could combine specialists, computing resources, its own models and a long investigation into a specific target. Automation lets it test more possibilities while people concentrate on the most promising findings. The NCSC also identifies highly capable state actors as those best placed to take full advantage of AI in sophisticated cyber operations. This is an assessment of capability and risk: OpenAI’s research does not establish that any particular intelligence service is already using these 948 findings. The NCSC’s assessment of state threats.
An organisation facing that kind of targeted attack should be wary of building its security around the assumption that it is simply too difficult to break into. It is more useful to limit the consequences of a breach in advance: separate systems and permissions, restrict access to secrets, watch for unusual activity and test the ability to recover. Patching schedules need to reflect actual risk as well as operational convenience.
AI can help defenders too. But a great deal of work remains between finding a bug and protecting a user: checking the report, preparing a sound fix, testing it and delivering the update. Linux developers specifically warn that inaccurate AI-generated reports overload maintainers and take time away from genuine problems. The Linux security team’s guidance.
The promise that “our system is secure” now demands some particularly uncomfortable follow-up questions: secure against which adversary, under what conditions, and how quickly will we notice if a protection fails? As vulnerability discovery and exploit development accelerate, the ability to contain the damage becomes as important as preventing the initial intrusion.
Написать Join — чтобы участвовать в обсуждении.
let an ordinary user gain root privileges > servers can continue working 😂😂😂
Ответы · 2
Yes, but if the Nginx user is able to execute arbitrary commands with superuser privileges, then it’s no longer your server.
Ответы · 2
bad...
Ответы · 1
Ответы · 3
Ответы · 1
Ответы · 2