{“lastseen”:”2026-02-18T22:06:12″,”description”:”What do advisory **USN-7545-1** and Windows updates **KB5065426** , **KB5063878** , **KB5055523** , and **KB5066835** have in common?\\n\\nBased on anonymized Qualys telemetry from 2025, they were among the **most frequently rolled-back patches** , in other words, patches that had to be undone after deployment.\\n\\nRollbacks aren\u2019t just inconvenient\u2014they\u2019re disruptive. They burn time, trigger outages, and create security gaps while teams scramble to stabilize production. And as patch volumes and critical vulnerabilities keep rising, the old approach\u2014\u201cdeploy and hope\u201d or \u201ctest everything forever\u201d\u2014doesn\u2019t scale.\\n\\nThat\u2019s why Qualys just released an important new capability in TruRisk Eliminate:\\n\\n## **Qualys Patch Reliability Score (AI-Powered)**\\n\\n**Patch Reliability Score** uses **AI** to help you answer a question every IT and security team asks right before rollout:\\n\\n**\u201cWhat are the chances this patch breaks something in my environment?\u201d**\\n\\nInstead of relying solely on release notes, forums, or guesswork, this feature provides an AI-driven reliability score that helps you **predict the operational risk of a patch.** This enables a risk-based patching strategy: move fast when it\u2019s safe, and slow down when it\u2019s not.\\n\\n \\n\\n## **How it works**\\n\\nAt any point in a patch\u2019s lifecycle, the reliability engine continuously evaluates **large-scale feedback signals gathered from many different public sources across the internet** \u2014including technical discussions, release-related feedback, and other real-world indicators that emerge after a patch ships.\\n\\nThe process runs:\\n\\n * **Immediately after a patch is released** , and\\n * **Continuously for weeks and months** (on an adjusted cadence)\\n\\n\\n\\nBecause of this continuous process, the score **evolves over time** as new information becomes available and the evidence set grows.\\n\\nThe output is simple and actionable:\\n\\n * **High Reliability Score** = Deploy sooner with confidence\\n * **Low Reliability Score** = Run additional testing, stage rollout, or delay broad deployment\\n\\n\\n\\nIn other words: **risk-based patching, powered by AI.**\\n\\n## **Proof Point: How the Reliability Score Performed Against 2025\u2019s Most Rolled-Back Patches**\\n\\nWhen Qualys Research analyzed the 2025 patches that were rolled back most often, we used those results to validate the new scoring capability.\\n\\nThe outcome: **the AI scored these patches as \u201cLow Reliability\u201d- matching what was ultimately experienced.**\\n\\nHere are a few examples:\\n\\n### **Advisory: USN-7545-1**\\n\\n**Title:** Ubuntu Security Notification for Apport Vulnerability (USN-7545-1) \\n**Reliability Score:** **Low** \\n**Why it mattered:** Addressed a vulnerability fix but was associated with regressions and follow-up advisories, increasing the likelihood of operational impact.\\n\\n* * *\\n\\n### **KB5063878**\\n\\n**Title:** August 12, 2025\u2014KB5063878 (OS Build 26100.4946) \\n**Reliability Score:** **Low** \\n**Why it mattered:** Customers reported serious post-update instability (crashes, app failures, update\/troubleshooter issues) and difficult recovery characteristics in some cases.\\n\\n* * *\\n\\n### **KB5065426**\\n\\n**Title:** September 9, 2025\u2014KB5065426 (OS Build 26100.6584) \\n**Reliability Score:** **Low** \\n**Why it mattered:** Reported installation\/uninstall complications and operational disruptions (connectivity and system behavior issues) that can derail broad deployments.\\n\\n* * *\\n\\n### **KB5055523**\\n\\n**Title:** April 8, 2025\u2014KB5055523 (OS Build 26100.3775) \\n**Reliability Score:** **Low** \\n**Why it mattered:** Deployment failures on some devices and authentication\/Windows Hello issues increased the \u201cpatch pain\u201d factor.\\n\\n* * *\\n\\n### **KB5066835**\\n\\n**Title:** October 14, 2025\u2014KB5066835 (OS Builds 26200.6899 and 26100.6899) \\n**Reliability Score:** **Low** \\n**Why it mattered:** Post-deployment issues reported across scenarios (e.g., recovery environment input devices, authentication\/cert workflows, and driver impacts), making staged rollout critical.\\n\\n## **Reliability + Mitigation: The Best of Both Worlds**\\n\\nHere\u2019s where this becomes a game-changer:\\n\\nSometimes you find a **critical vulnerability** , but the **patch reliability is low**.\\n\\nHistorically, teams had to choose whether to:\\n\\n * **Patch now and risk breaking production** or\\n * **Delay patching and accept exposure**\\n\\n\\n\\nNow you don\u2019t have to choose.\\n\\n## **Use Patch Reliability Score side-by-side with Qualys mitigation capabilities**\\n\\nIf a critical vulnerability is detected and the patch is low reliability, customers can use **Qualys-curated mitigation techniques** to **reduce or block the security risk** while the patch is:\\n\\n * thoroughly tested\\n * staged\\n * and safely deployed\\n\\n\\n\\nThis enables a practical, real-world strategy:\\n\\n * **Reduce risk immediately (mitigate)**\\n * **Patch safely when ready (deploy confidently)**\\n\\n\\n\\n* * *\\n\\n**Access the Getting Started Guide to see how easy it is to get started with TruRisk Mitigate.**\\n\\nRead Now\\n\\n* * *\\n\\n## **The Bottom Line**\\n\\nPatch management isn\u2019t just about _speed_ anymore\u2014it\u2019s about **predictability**.\\n\\nWith the new **AI-powered Patch Reliability Score** , Qualys helps customers:\\n\\n * anticipate patch instability before it becomes an outage\\n * prioritize testing effort where it\u2019s most needed\\n * deploy faster when confidence is high\\n * and stay protected using mitigations when patch risk is high\\n\\n\\n\\n**Less guessing. Fewer rollbacks. Better security outcomes.**\\n\\n## How to Experience the Patch Reliability Score\\n\\n * If you have **Qualys Eliminate** , this new capability is **already included** in your solution.\\n * If you don\u2019t, ask your **TAM** to **enable a trial** , so you can evaluate Patch Reliability Score in your environment.\\n * New customers: Reach out to us or sign up for a trial of Eliminate today.\\n\\n\\n\\n## **Frequently Asked Questions**\\n\\n**Q: How do I access the Patch Reliability Score?** _A: If you are a Qualys Eliminate customer, this capability is already included. If not, contact your Technical Account Manager (TAM) to enable a trial.\\n\\n**Q: Does the score change over time?** _A: Yes. The reliability engine continuously updates the score as new feedback and data become available after the initial patch release.\\n\\n**Q: Can I automate deployments based on the score?** _A: Yes. The score effectively enables risk-based patching, allowing teams to set policies that accelerate high-reliability patches and pause low-reliability ones for testing.”,”published”:”2026-02-18T21:35:23″,”modified”:”2026-02-18T21:35:23″,”type”:”qualysblog”,”title”:”New: AI-Powered Patch Reliability Scoring\u2014Predict Patch Impact Before You Deploy”,”source”:””,”references”:””,”id”:”QUALYSBLOG:0FBD639172CABB4B986F987C2057FA66″,”bulletinFamily”:”blog”,”cwe”:null,”cvelist”:[],”sourceData”:””,”sourceHref”:””,”cvss”:{“score”:0,”severity”:”NONE”,”vector”:”NONE”,”version”:”NONE”},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:”https:\/\/blog.qualys.com\/category\/product-tech”,”category_name”:”News”,”post_link”:””,”product”:””,”version”:””,”vendor”:””,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:”2026-02-18T22:06:12″,”description”:”What do advisory **USN-7545-1** and Windows updates **KB5065426** , **KB5063878** , **KB5055523** , and **KB5066835** have in common?\\n\\nBased on anonymized Qualys telemetry from 2025, they…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,12,13,33,120,7,11,5],"class_list":["post-41473","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-exploit","tag-news","tag-none","tag-qualysblog","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n