Urgent.News

What's breaking now, across thousands of outlets.

Tech

Mythos has made 2026 patching hell. It might make 2027 a breeze

Gartner sees huge amounts of technical debt paid down, and better scanning that could make software safer sooner

Mythos has made 2026 patching hell. It might make 2027 a breeze

Microsoft released over 970 patches in a single week, causing concern for IT security teams. Gartner research vice president Craig Lawson believes that the widespread use of AI tools like Anthropic’s Mythos may soon make patching a simpler process. Lawson pointed out that AI has never before been used to audit such large codebases, and referenced the recent CVEs found in OpenBSD as evidence of this.

He also mentioned that security vendors are using AI to find bugs in their own products, indicating that AI is eradicating potential zero-day attack avenues. Lawson expects that in 2027, we may see a net decrease in CVE numbers, not in total vulnerabilities, but in severity. Additionally, he believes AI will enhance defenders' tools, allowing for daily red team exercises, and suggesting that automated fixes using AI could be created.

He hopes that organizations will acknowledge the impact of their security teams, rather than solely focusing on the number of tickets processed and closed.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at theregister.com →

More in Tech

Can You Vibe Code an OS Without Lying to Yourself?

I have no idea what I'm f*cking doing. Something I have been chewing on: I am using AI agents to help build an operating system. And I genuinely cannot tell you yet whether that is a good idea.

  • ShrekOS boots, updates, and isolates agents.
  • AI agents work within defined framework.
  • Vibe coding operating system is potentially irresponsible.

A Green Local Test Can Hide a Broken Project Graph

“The tests pass on my machine” is often treated as a testing problem. Sometimes it is really a dependency-graph problem. Consider a browser application that contains a small deterministic rule: given…

  • Local tests pass but CI fails due to build contract differences.
  • Test project imports application head, bringing build graphs and property-sensitive behavior.
  • Refactor by moving rule to neutral library for both application and test project.

More from Wednesday 16 September →