As tools like Claude Mythos accelerate vulnerability discovery, vendors will ship patches, dependency updates, and revised releases for months. The question isn't whether the wave comes, it's whether your process can absorb it. The time to prepare is before it lands.

“A lot of the conversation around Claude Mythos is focused on vulnerability discovery. The operational impact may be the bigger story for enterprise application management teams.”
Bob Kelly, Chief Product Officer, Juriba
Get access to your own instance of App Readiness, and we'll package, test, and publish a sample set of your apps with you - within a week.
AI-assisted vulnerability discovery is accelerating. Claude Fable 5 is generally available now; Claude Mythos, the frontier, cyber-capable model, is currently restricted to Anthropic's Project Glasswing partners, with broader access coming.
Either way, as these tools expose deeper issues across widely used software, vendors will respond with patches, dependency updates and revised releases: a sustained wave that organisations must assess, test and deploy. It begins now and continues for months as vendors respond at different speeds. The practical enterprise story isn't the discovery. It's the wave that follows, and whether you're ready for it.

From Juriba's State of the Windows Application Packaging Nation report (June 2026) - enterprise teams are already under pressure before the wave peaks.
Many organizations struggle to keep applications updated within three months.
The average time from a patch being available to being deployed across the enterprise.
of the Windows estate has no owner and no patch path — invisible to a catalogue.
Number of breaches stemming from known, unpatched vulnerabilities (Ponemon Institute).
Including apps that never appear in a patch catalog.
Automated testing compresses the request-to-deploy timeline dramatically.
Selective, mostly manual patching becomes very hard to defend when update volume, security urgency, and operational complexity all rise at once. The resilient response is an evergreen process that continuously absorbs change.
SPEED - ACCELERATE
5-20 days to package & test; 42-day deployment lag
COVERAGE - CONNECT
Catalogs cover 20-30; the rest is manual or invisible
EVIDENCE - GUARDIAN
"Was it tested?" = a sign-off email
POSTURE - SECURE
Patching is an occasional, selective event
SPEED - ACCELERATE
Hours, not days. Up to 80% automated
COVERAGE - CONNECT
Up to 100% - incl. the 70-80% catalogs don't touch
EVIDENCE - GUARDIAN
One-click, time-stamped proof per app (video, logs, exit codes)
POSTURE - SECURE
Continuous operational discipline - evergreen
Automate the repeatable; reserve your specialists for the complex tasks
Packaging and testing across the estate, including the 70-80% of applications no catalog touches, via AI-driven repackaging when no silent install exists
Automated smoke testing runs in minutes, dramatically compressing the request-to-deploy timeline
Direct publishing to Intune and MECM, with no manual intervention for routine updates
Skilled packagers focus on the complex exceptions; the repeatable work runs itself
Follow a clear, proven journey to expose unmanaged risk, measure its impact, and build lasting auditable governance.

"The answer is not panic. The answer is throughput. Application patching can no longer be treated as occasional, selective, or mostly manual. It has to become a continuous operational discipline.
Bob Kelly
Chief Product Officer, Juriba • 3x Microsoft MVP - Read his blog →
This section will display 3+ of your most recent articles. Including this section at the bottom of the home page helps reduce bounce rate and gives users a place to go if they're not ready to convert.
Still have questions?
Your own instance of App Readiness. We package, test, and publish a sample set of your real applications with you, typically within a week, so you can see it work on the apps you care about.
No. The guided trial runs in your own hosted instance with Juriba-managed test VMs.
No tool does. Juriba closes the patch-velocity and coverage gap that the coming Mythos wave will expose. Vendor fixes are packaged, tested, and deployed in hours, not weeks.
Most organizations spend weeks on manual packaging and smoke testing. With automation, repetitive steps like wrapping, virtual machine testing, and basic UAT are completed in minutes. This cuts packaging request turnaround times by up to 80% and allows IT to handle volumes that would otherwise be impossible.
Without automation and governance, backlogs grow, security patches are delayed, and unmanaged “shadow IT” apps creep in. This leads to higher costs, compliance risks, and frustrated business users waiting weeks for updates. The longer you wait, the harder it becomes to catch up.
Juriba integrates directly with Intune, MECM, and ServiceNow. We don’t replace them—we extend them with automation, orchestration, and governance. That means you keep the investments you’ve already made, while getting the speed and visibility those platforms don’t provide on their own.