News for hackers. Stuff that matters.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by dvh on Wednesday November 18, 2026 @11:58AM (#50548739)
Not necessarily. Only if you assume that no new insecure code is added. If ai found 1 security bugs in old code but ease of code generation with ai adds 2 new security issues (in unrelated code), then we are getting less secure.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by SOLAR_FIELDS on Wednesday November 18, 2026 @11:59AM (#50548752)
Do we have any evidence around the rate that AI emits security bugs vs humans previously? You would think that perhaps AI would be better about this, but perhaps not.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by dvh on Wednesday November 18, 2026 @12:05PM (#50548833)
I'm making no claims. I'm just saying that contributing before ai was difficult so people rarely did it. Now that contributing is easy, more code will be added. More code = more bugs. Always.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by voakbasda on Wednesday November 18, 2026 @12:42PM (#50549450)
Yet the opposite seems to be true. Many projects now shun new contributors due to AI.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by hparadiz on Wednesday November 18, 2026 @12:57PM (#50549671)
I've run Daybreak against my human written pre-AI code and found so much stuff that I don't trust human or AI written code. It all MUST be audited by a security sweep AI.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by punchmesan on Wednesday November 18, 2026 @01:04PM (#50549771)
Eh I'm not sure that's an indicator that the opposite is true. Github's vastly increased commit activity is the best indicator we have of this. https://www.tomshardware.com/software/github-report-highligh...

Sure, some projects are trying to be responsible or are trying to keep waves of slop PR's from drowning them, but that is by no means an indication of a general distaste for AI code. It's been largely embraced.

Re:CVE-2026-99312: KVM Guest-to-Host Escape by ranger_danger on Wednesday November 18, 2026 @03:48PM (#50551927)
Are any of those large projects used by many people?
Re:CVE-2026-99312: KVM Guest-to-Host Escape by the8472 on Wednesday November 18, 2026 @12:15PM (#50549008)
[delayed]
Re:CVE-2026-99312: KVM Guest-to-Host Escape by j45 on Wednesday November 18, 2026 @12:04PM (#50548820)
Existing code will have security holes that haven't been found yet.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tptacek on Wednesday November 18, 2026 @12:18PM (#50549062)
I hate these meta conversations on crunchy technical topics and feel like we should be digging into the KVM security model more than this general security prognostication stuff. Having said that, I will hypocritically further this debate by pointing out that the determinant of software security moving forward is not so whether AI is drastically better than humans at avoiding common vulnerability patterns, (or instead just a little better). Rather, it's that AI will make it much easier to move subsystems or whole projects to memory-safe programming languages and towards formal verification.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tyingq on Wednesday November 18, 2026 @12:33PM (#50549299)
Is it a given that it's as good at outputting secure code as it finding insecure code? That leaves a fair amount of room for people not baking in deep review steps. Also mentioned elsewhere, but if velocity is way up...that ramps up bugs anyway.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by MajesticHobo2 on Wednesday November 18, 2026 @12:38PM (#50549386)
No, it's not a given. AI always finds security issues in the things I just had it write.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by hparadiz on Wednesday November 18, 2026 @12:56PM (#50549660)
This is true for human written code too. This is why in the future all written code MUST be run through an internal security sweep before being given to your harness for writing. That's just basic due diligence at this point.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by catlifeonmars on Wednesday November 18, 2026 @01:18PM (#50549946)
[delayed]
Re:CVE-2026-99312: KVM Guest-to-Host Escape by vbezhenar on Wednesday November 18, 2026 @01:35PM (#50550202)
As long as model providers deny access to security-capable models, it can't be basic diligence.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by hparadiz on Wednesday November 18, 2026 @01:39PM (#50550261)
This is something agents already do as part of their normal work. Providing code that you know is vulnerable is in fact a dereliction of duty and negligence. Don't provide a POC. Simply that as it produces code a background agent just checks it without showing the work and points out potential problems.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by greyr0ck on Wednesday November 18, 2026 @02:24PM (#50550827)
The slop is cheap but checking will cost extra, what a pricing scheme! Modern day Pharo level of lockin!
Re:CVE-2026-99312: KVM Guest-to-Host Escape by FrinkleFrankle on Wednesday November 18, 2026 @04:18PM (#50552247)
But that should be part of your pipeline, no? Personally, the thing I've spent the most time working on with AI is.. a stack to get AI to keep a project on track and follow strict code writing standards that are reviewed. Not everyone is working in that, but I'm sure any serious development will be done via something similar.

Although, at the pace of improvement, I'd bet it won't even be necessary in a year or so.