{"id":22327,"date":"2026-07-17T10:07:25","date_gmt":"2026-07-17T10:07:25","guid":{"rendered":"https:\/\/www.securitytoday.de\/2026\/07\/17\/622-cves-prioritize-over-panic-patching\/"},"modified":"2026-09-29T08:39:08","modified_gmt":"2026-09-29T08:39:08","slug":"622-cves-prioritize-over-panic-patching","status":"publish","type":"post","link":"https:\/\/www.securitytoday.de\/en\/2026\/07\/17\/622-cves-prioritize-over-panic-patching\/","title":{"rendered":"622 CVEs: Prioritize Over Panic Patching"},"content":{"rendered":"<p style=\"color:#69d8ed;font-size:0.9em;margin:0 0 16px;padding:0;\">5 Min. Reading time<\/p>\n<p><strong>Microsoft&#8217;s July 2026 Patch Tuesday lists 622 CVEs &#8211; record volume. Anyone planning everything &#8220;immediately&#8221; is courting chaos. Those prioritizing AD FS (Active Directory Federation Services), On-Premises SharePoint and physically accessible endpoints first steer the change window.<\/strong><\/p>\n<div style=\"background:#003340;color:#fff;padding:32px 36px;margin:32px 0;border-radius:8px;\">\n<p style=\"margin:0 0 18px 0;font-size:0.95em;font-weight:800;text-transform:uppercase;letter-spacing:0.2em;color:#69d8ed;border-bottom:2px solid rgba(105,216,237,0.25);padding-bottom:12px;\">Key Takeaways<\/p>\n<ul style=\"margin:0;padding-left:22px;color:rgba(255,255,255,0.92);line-height:1.6;\">\n<li style=\"margin-bottom:12px;\"><strong style=\"color:#69d8ed;\">First exploit signal.<\/strong> Actively exploited AD FS and SharePoint vulnerabilities ahead of breadth and CVSS racing.<\/li>\n<li style=\"margin-bottom:12px;\"><strong style=\"color:#69d8ed;\">Then exposure.<\/strong> Internet-facing and identity stack before internal clients without a lateral path.<\/li>\n<li><strong style=\"color:#69d8ed;\">BitLocker and Client EoP (Endpoint Protection) tracked separately.<\/strong> Physical access and local privileges require separate owners and separate change windows.<\/li>\n<\/ul>\n<\/div>\n<p style=\"font-size:0.88em;color:#666;margin:20px 0 32px 0;border-top:1px solid #e5e5e5;border-bottom:1px solid #e5e5e5;padding:10px 0;\">\n<span style=\"color:#004a59;font-weight:700;text-transform:uppercase;font-size:0.72em;letter-spacing:0.14em;margin-right:14px;\">Related:<\/span><br \/>\n<a href=\"https:\/\/www.securitytoday.de\/en\/2026\/07\/15\/sharepoint-jwt-bypass-exposes-on-premises-sites\/\" style=\"color:#333;text-decoration:underline;\">SharePoint JWT Bypass Opens On-Premises Sites<\/a>&nbsp;&nbsp;<span style=\"color:#ccc;\">\/<\/span>&nbsp;&nbsp;<a href=\"https:\/\/www.securitytoday.de\/en\/2026\/07\/15\/bitlocker-bypass-physical-access-cve-2026-50661\/\" style=\"color:#333;text-decoration:underline;\">BitLocker Bypass via Physical Access<\/a>\n<\/p>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">Why 622 Isn&#8217;t a Patch Strategy<\/h2>\n<p><strong>What is Patch Tuesday prioritization?<\/strong> Patch Tuesday prioritization sorts monthly Microsoft updates by proven exploitation and attack surface rather than by CVSS score or catalog order. Actively exploited gaps in internet-facing identity and collaboration systems take priority, with breadth following in rings. The goal is reliable P0 coverage within the tight change window, not completing an entire catalog in 48 hours.<\/p>\n<p>On July 14, 2026, Microsoft released fixes for 622 vulnerabilities &#8211; the largest known Patch Tuesday package &#8211; according to the Security Update Guide and industry analyses. Among them are actively exploited gaps in Active Directory Federation Services and on-premises SharePoint Server, publicly discussed BitLocker bypass topics, and hundreds of Windows findings.<\/p>\n<p>Volume creates board pressure and ticket avalanches. It doesn&#8217;t create priority. Priority arises from exploit status, accessibility, privilege path, and business impact. Those who process the list linearly burn the scarce change window on client noise, while identity and collaboration stacks remain exposed.<\/p>\n<div data-element=\"key_number\" style=\"background:#003340;border:1px solid rgba(105,216,237,0.28);border-radius:10px;padding:28px 24px;margin:32px 0;text-align:center;\">\n<div style=\"font-size:2.6em;font-weight:800;color:#69d8ed;line-height:1.05;word-break:keep-all;\">622<\/div>\n<p style=\"margin:10px 0 0;font-size:0.92em;color:#e6e3da;\">CVEs in July-2026 Patch Tuesday (according to MSRC Security Update Guide and Patch Tuesday analyses, 14.07.2026)<\/p>\n<p style=\"margin:6px 0 0;font-size:0.78em;color:#8fa3ab;\">Source: Microsoft Security Update Guide \/ Patch Tuesday analyses 14.07.2026<\/p>\n<\/div>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">Prioritization Ladder for DACH Environments<\/h2>\n<p><strong>Stage 1 &#8211; actively exploited, both in CISA KEV (Known Exploited Vulnerabilities).<\/strong> AD FS (including CVE-2026-56155 per MSRC Security Update Guide) and SharePoint Server (including CVE-2026-56164) take top priority in every playbook. The attack vectors differ markedly: SharePoint can be attacked unauthenticated over the network, whereas AD FS requires a local foothold with a valid account. For AD FS, the July KB does not resolve the issue alone. It initially audits the ACL of the DKM container, with automatic remediation scheduled only for the October 13, 2026 update. Identity and Document Hubs are the classic pivot for ransomware and data theft. On-premises SharePoint with internet exposure is a separate escalation ticket, not a maintenance item.<\/p>\n<p><strong>Stage 2 &#8211; Internet-facing and Hybrid Identity.<\/strong> Exchange, AD FS proxies, reverse proxies, VPN entry points, publicly reachable SharePoint web apps. Here, patching plus hardening is required: shut down unnecessary endpoints, verify MFA and Conditional Access, log for compromise indicators.<\/p>\n<p><strong>Stage 3 &#8211; Endpoint and Physical Exposure.<\/strong> BitLocker bypass and local privilege escalation (including publicly discussed PoCs after the patch tag) require separate tracks: laptops with theft risk, admin workstations, jump hosts. This is not the same queue as the SharePoint farm patch.<\/p>\n<p><strong>Stage 4 &#8211; Broad Scope.<\/strong> Remaining Windows, Office, and developer tool fixes by asset class and maintenance window. Here automation and ring deployments are used; this does not require the entire incident team&#8217;s night.<\/p>\n<div style=\"overflow-x:auto;-webkit-overflow-scrolling:touch;margin:16px 0 32px 0;\">\n<table style=\"width:100%;min-width:560px;border-collapse:collapse;font-size:0.95em;\">\n<thead>\n<tr style=\"background:#003340;color:#fff;\">\n<th style=\"padding:12px 16px;text-align:left;border:1px solid #003340;\">Priority<\/th>\n<th style=\"padding:12px 16px;text-align:left;border:1px solid #003340;\">Focus<\/th>\n<th style=\"padding:12px 16px;text-align:left;border:1px solid #003340;\">Owner Type<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\"><strong>P0<\/strong><\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\">AD FS \/ SharePoint with Exploit Signal<\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;color:#003340;font-weight:600;\">IAM + Collaboration, 24\/48h<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\"><strong>P1<\/strong><\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\">Internet-facing Hybrid Stack<\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;color:#003340;font-weight:600;\">Infra + SOC Hunting<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\"><strong>P2<\/strong><\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\">BitLocker \/ Local Endpoint Privilege Escalation (EoP) on High-Risk Hosts<\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;color:#003340;font-weight:600;\">Endpoint + Security<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\"><strong>P3<\/strong><\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;\">Remaining Scope by Asset Class<\/td>\n<td style=\"padding:12px 16px;border:1px solid #ddd;color:#003340;font-weight:600;\">Patch Operations \/ Rings<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"font-size:0.8em;color:#888;margin:8px 0 0;\">Source: SecurityToday Prioritization Model, based on MSRC Exploit Flags July 2026<\/p>\n<\/div>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">Controlling Change Windows Instead of Reporting Them<\/h2>\n<p>A record Patch Tuesday demands a communications template for leadership and business units: What exactly is a P0, why does it matter, what risk remains until P1, and which systems are frozen. Without this narrative, every ticket escalates at the same volume-and the truly critical stack gets lost.<\/p>\n<p>Technically: Ring 0 for identity and collaboration servers with Pre-Prod Canary, then critical servers, then workstations. Measured by the percentage of patched assets per P\u2011stage, not just \u201ctickets closed\u201d. SOC works in parallel: hunting for AD\u2011FS and SharePoint compromise traces from the pre\u2011patch window, not only after the final client reboot.<\/p>\n<div data-element=\"checklist\" style=\"background:#23261f;border:1px solid rgba(105,216,237,0.22);border-radius:10px;padding:22px 24px;margin:32px 0;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 2px 10px rgba(0,0,0,0.22);\">\n<p style=\"margin:0 0 12px;font-family:'IBM Plex Mono',ui-monospace,SFMono-Regular,monospace;font-size:0.72em;letter-spacing:0.12em;text-transform:uppercase;color:#69d8ed;\">RUNBOOK MINIMUM<\/p>\n<ul style=\"margin:0;padding-left:0;list-style:none;\">\n<li style=\"margin:0 0 10px;padding-left:26px;position:relative;color:#e6e3da;line-height:1.5;\"><span style=\"position:absolute;left:0;color:#69d8ed;\">&#10003;<\/span>P0 Assets inventory (Active Directory Federation Services (AD FS), SharePoint farms, Exposure)<\/li>\n<li style=\"margin:0 0 10px;padding-left:26px;position:relative;color:#e6e3da;line-height:1.5;\"><span style=\"position:absolute;left:0;color:#69d8ed;\">&#10003;<\/span>Canary patch + rollback plan before mass rollout<\/li>\n<li style=\"margin:0 0 10px;padding-left:26px;position:relative;color:#e6e3da;line-height:1.5;\"><span style=\"position:absolute;left:0;color:#69d8ed;\">&#10003;<\/span>SOC hunting queries for pre\u2011patch windows start<\/li>\n<li style=\"margin:0;padding-left:26px;position:relative;color:#e6e3da;line-height:1.5;\"><span style=\"position:absolute;left:0;color:#69d8ed;\">&#10003;<\/span>Board update: P0 status, residual risk, next window<\/li>\n<\/ul>\n<\/div>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">Distinction from Single Advisories<\/h2>\n<p>Individual articles on SharePoint-JWT, BitLocker or post-patch PoCs remain valid. This text serves as the prioritization layer on top: how to sort a massive volume of tickets without fragmenting the situation into 622 equally loud items. Those who have already handled the individual topics use them as P0\/P2 documentation-not as a replacement for the staircase.<\/p>\n<p>Those who take the staircase separate board communication from the ticket mountain: leadership receives P0 coverage and residual risk instead of the raw count of CVEs. At the same time, the single advisories on SharePoint, BitLocker and post-patch PoCs remain the detailed runbooks. This text merely controls the order within the narrow change window.<\/p>\n<h2 style=\"padding-top:64px;margin-bottom:20px;\">Frequently Asked Questions<\/h2>\n<p class=\"st-faq-hint\">Every question is locked. A tap unlocks the answer.<\/p>\n<details>\n<summary><strong>Must everything really be done within 48 hours?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">No. Prioritize actively exploited and internet-facing identity and collaboration systems first. Scale follows in rings.<\/p>\n<\/details>\n<details>\n<summary><strong>Is CVSS sufficient for sorting?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">No. Exploit status and exposure outperform pure score lists. A moderate score with active exploitation wins against critical, but isolated client bugs.<\/p>\n<\/details>\n<details>\n<summary><strong>Where do I assign BitLocker?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">For endpoints that face physical theft or access risk as a separate P2 track &#8211; parallel, but not before the P0 identity stack.<\/p>\n<\/details>\n<details>\n<summary><strong>What should I report to management?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">P0 coverage in percent, open internet-facing assets, residual risk until next window &#8211; not the raw number 622.<\/p>\n<\/details>\n<details>\n<summary><strong>Does prioritization replace the single-patch article?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">No. It controls the order. Technical details remain in the respective advisories and runbooks.<\/p>\n<\/details>\n<p><!--ST-LOWER-CARDS lang=en--><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">Editor&#8217;s Picks<\/h3>\n<p><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/07\/15\/cursor-launches-git-exe-from-repo-root-windows\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/cursor-windows-git-exe-repo-root-code-execution-cover-hero-250x141.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Cursor Launches git.exe from Repository Root on Windows<\/span><\/span><\/a><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/07\/15\/legacyhive-poc-latest-windows-patches\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/legacyhive-windows-eop-poc-nach-patch-tuesday-cover-hero-250x141.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">LegacyHive PoC Meets Latest Windows Patches<\/span><\/span><\/a><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/07\/15\/two-joomla-upload-vulnerabilities-added-to-cisa-kev\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/joomla-icagenda-balbooa-kev-upload-rce-cover-hero-250x141.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Two Joomla Upload Vulnerabilities Added to CISA KEV<\/span><\/span><\/a><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">More from the MBF Media Network<\/h3>\n<p><a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/07\/16\/when-ai-agents-travel-data-residency-as-an-operating-problem\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/09\/net-when-ai-agents-travel-data-residency-as-46681309.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#0bb7fd;margin-bottom:5px;\">cloudmagazin<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">When AI Agents Travel: Data Residency as an Operating Problem<\/span><\/span><\/a><a href=\"https:\/\/mybusinessfuture.com\/en\/more-insolvencies-smaller-cases-what-counts\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/09\/net-more-insolvencies-smaller-cases-what-cou-22218328-250x143.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#aa8ac2;margin-bottom:5px;\">MyBusinessFuture<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">More insolvencies, smaller cases: What counts<\/span><\/span><\/a><a href=\"https:\/\/www.digital-chiefs.de\/en\/token-opex-inference-controls-not-the-seat-budget\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-token-opex-inference-steuert-nicht-das-s-43794747-250x141.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#e8828d;margin-bottom:5px;\">Digital Chiefs<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Token-OPEX: Inference Controls, Not the Seat Budget<\/span><\/span><\/a><!--\/ST-LOWER-CARDS--><\/p>\n","protected":false},"excerpt":{"rendered":"Record Patch Tuesday with 622 CVEs. Prioritize AD FS and SharePoint first, then exposure, then breadth\u2014this controls the change window.","protected":false},"author":50,"featured_media":22233,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_focuskw":"patch Tuesday prioritization","_yoast_wpseo_title":"622 CVEs: Prioritize Over Panic Patching","_yoast_wpseo_metadesc":"Microsoft's July Patch Tuesday with 622 CVEs: prioritize by exploit and exposure over linear catalog processing.","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"evm_kih_original":false,"_evm_slot_owner":"","evm_cvss":0,"evm_risk":0,"evm_casefile":"","evm_primary_cve":"","evm_pin_until":0,"evm_external_preview_token":"","evm_external_preview_expires":"","_evm_translation_lang":"en","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[255],"tags":[],"class_list":["post-22327","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-praxis-umsetzung-en"],"evm_reading_time_minutes":6,"wpml_language":"en","wpml_translation_of":22224,"_links":{"self":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/22327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/comments?post=22327"}],"version-history":[{"count":2,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/22327\/revisions"}],"predecessor-version":[{"id":24274,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/22327\/revisions\/24274"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media\/22233"}],"wp:attachment":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media?parent=22327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/categories?post=22327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/tags?post=22327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}