{"id":3890,"date":"2025-09-17T07:06:53","date_gmt":"2025-09-17T04:06:53","guid":{"rendered":"http:\/\/147.182.243.37\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/"},"modified":"2025-09-17T07:06:53","modified_gmt":"2025-09-17T04:06:53","slug":"microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed","status":"publish","type":"post","link":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/","title":{"rendered":"Microsoft Patch Tuesday de setembro \u2013 Duas vulnerabilidades de dia zero e 81 bugs corrigidos"},"content":{"rendered":"

<\/p>\n

Apply the updates now<\/strong> to neutralize the two zero-day vulnerabilities and the 81 fixes released this Patch Tuesday. Quick deployment minimizes exposure across devices, and reduces the risk of exploitation that can spread like sepsis through an unpatched environment.<\/p>\n

first<\/em>\u2013the two zero-day vulnerabilities pose high risk with potential for remote code execution, privilege escalation, and bypass of protections. The fixes cover multiple components, including win32k, so prioritize systems with graphic subsystem exposure. Review the information and prepare for a fast, staged rollout using your existing deployment tools. For more information, refer to the official Microsoft guidance.<\/p>\n

Administrators should map the patches to the papel<\/em> requirements of their fleet, focusing on high-risk endpoints and servers. Use a multi-stage<\/strong> process: test in a \u0442\u0435\u0440\u043c\u0438\u043d\u0430\u043b sandbox, then forward the update to production with \u0438\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u0430\u044f configurations and \u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u0435 plans. Ensure a rollback path in case of driver compatibility issues.<\/p>\n

For enterprises, plan a fast<\/strong>, coordinated rollout that covers Windows client, server, and cross-architecture environments. Use the update information to confirm that the packages align in the same release bundle, then \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 the patches through your centralized tooling to ensure a smooth \u043d\u043e\u0441\u0438\u043b\u044c\u0449\u0438\u043a\u0430 function across endpoints. Enable logging and validate the deployment with targeted checks and a quick<\/em> forward review of permissions and service states.<\/p>\n

After deployment, monitor<\/strong> for bypass attempts, unusual process behavior, and network anomalies. Enable centralized information dashboards and fast<\/em> alerts, and review logs for exploitation signs in win32k and related components. Maintain a clear change-management trail for \u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u0435 audits and document follow-up actions for \u0442\u0435\u0440\u043c\u0438\u043d\u0430\u043b and remote \u043d\u043e\u0441\u0438\u043b\u044c\u0449\u0438\u043a\u0430 endpoints to close gaps quickly.<\/p>\n

Zero-Day Details: CVEs, Affected Products, and Exploit Indicators<\/h2>\n

Apply the updates now to close the two zero-day vulnerabilities and prevent exploitation across Windows devices, Hyper-V hosts, and Xbox endpoints. The Security Update Guide lists CVEs tied to these flaws and details affected products across the compute and infrastructure stack. Validate that all devices, servers, and virtualization hosts receive the patch cycle, and plan deployment across trials in test environments before broad rollout in production within your projects.<\/p>\n

Two zero-day vulnerabilities are tracked in this release. The CVEs are documented in the bulletin, with affected products spanning Windows client and server OS, Hyper-V, and related compute components. Microsoft emphasizes updating both host and guest environments, as well as firmware for relevant drivers and devices that participate in the virtualization stack. Montr\u00e9al-based security teams and proponents of defense-in-depth should coordinate cross-team updates to minimize downtime and preserve resilience of critical services.<\/p>\n

Exploit Indicators and Mitigation<\/h3>\n

Exploitation indicators include driver-level interactions, elevated processes, and unusual hypervisor activity. Monitor for spikes in kernel-mode events, abnormal SMB traffic, and unexpected PowerShell commands. Telemetry should correlate with CVE advisories and update status checks. After patching, run a controlled set of tests in a trials environment to verify that services resume normally and that compute workloads function as expected. Maintain a care plan for infrastructure resilience across Xbox devices and other endpoints, and document progress in ongoing projects.<\/p>\n

Bug Breakdown: Severity, Affected Components, and Fixes Across Windows, Office, and Browser Engines<\/h2>\n

Patch Windows, Office, and browser engines now to block two zero-day vulnerabilities and apply 81 fixes across the stack. Start with critical devices, then roll out to laptops and servers, and verify installation with telemetry that patch levels show as installed. include a staged rollout plan with checkpoints and rollback options.<\/p>\n

Severity snapshot: two zero-days are \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f; one targets win32k surfaces, the other affects browser engine interfaces. Together they create a risk of remote code execution and privilege escalation on exposed endpoints. The fixes emphasize memory safety, input validation, and sandbox hardening to limit impact, using a sepsis-like urgency to drive containment and validation.<\/p>\n

Affected components: Windows core includes win32k and related UI, graphics, and kernel surfaces; Office coverage spans Word, Excel, and Outlook with templates and macros; Browser engines address Chromium-based render paths used by Edge and other Chromium browsers, mitigating use-after-free and memory corruption in decoding paths. Patches span kernel-mode, user-mode, and runtime libraries, reflecting a construction of layered security hardening across the platform.<\/p>\n

Fixes and verification: after installing updates, reboot devices and run a focused test plan that includes opening common documents, executing safe macros, and loading representative websites. Use non-invasive monitoring to confirm patch status, and verify via telemetry that win32k, Office, and browser components show updated build numbers. The approach balances reliability and security, with retinoids-like precision that minimizes downtime while delivering meaningful protection.<\/p>\n

Operational guidance: coordinate with montreal teams and the service desk to align deployment windows. Include \u043f\u0430\u0441\u043f\u043e\u0440\u0442\u043d\u043e\u0433\u043e clearance and relevant \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u043e\u0432 for approvals. For \u0442\u0443\u0440\u0438\u0441\u0442\u043e\u0432 visiting offices, provide patch briefings and ensure devices are patched before they connect to the corporate network. Deployment packages \u043f\u0440\u0438\u043b\u0451\u0442\u0435 through secure channels. If RRAS endpoints exist, include them in the patch scope (rras). Use xbox labs and other testing environments as \u043f\u0440\u043e\u0435\u043a\u0442\u044b to validate updates, and document lessons learned in information channels. Assign a representative (\u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u0442\u0435\u043b\u0435\u043c) to answer questions via phone, and ensure that \u0443\u0441\u043b\u0443\u0433\u0438 and machine images stay up to date in ongoing projects. That information helps reduce \u0431\u0430\u0433\u0430\u0436\u0430 and keep stakeholders informed.<\/p>\n

Mitigation Playbook: Patch Timelines, Restart Requirements, and Safe Rollout Strategies<\/h2>\n

Patch the two zero-days within 24 hours on all exposed endpoints, then roll out in three phases: lab validation, pilot cohort, and organization-wide deployment. Use Windows Update for Business with deployment rings and a clear rollback path; include win32k fixes and drivers for grfx and bluetooth in the same policy to prevent post-install issues, and account for \u0441\u0442\u043e\u0438\u043c\u043e\u0441\u0442\u044c and \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u0435 overhead in your budget. This approach delivers that high safety while keeping deployment cadence predictable.<\/p>\n

Patch Timelines and Staging<\/h3>\n

0\u201324 hours: patch critical items on exposed endpoints within the first \u043f\u0443\u043d\u043a\u0442\u0430 cohort and perform lab validation for win32k, grfx, visio, and bluetooth workloads. 24\u201372 hours: expand to a pilot set across key departments and Montreal sites and at \u0430\u044d\u0440\u043e\u043f\u043e\u0440\u0442\u0430 campuses, validating workflows and compatibility with common apps. 3\u20137 days: complete organization-wide rollout to the largest sites, including edge devices; monitor for regressions and keep a rollback ready if necessary. Use an extended maintenance window for devices with complex configurations and simulate real-use conditions, including \u0440\u0435\u0439\u0441 schedules to test cross-site resilience.<\/p>\n

Restart Requirements and Safe Rollout<\/h3>\n

Restart policy centers on minimizing user impact. Require reboot after patch on most devices, but enable auto-restart only within a defined maintenance week window. Implement three deployment rings: canary, pilot, and wide, and keep a rollback plan that can be executed within one week if you detect critical issues. For devices with ongoing tasks or specialized workloads (retinoids imaging pipelines), use a controlled postpone option and document the reason in the change log. Monitor safety signals such as crash reports and service availability, and keep stakeholders informed using visio or other tracking tools; this approach reduces downtime and protects critical operations while you address \u0432\u0430\u0436\u043d\u044b\u0445 issues quickly.<\/p>\n

Validation and Verification: How to Confirm Patch Status and Detect Signs of Exploitation<\/h2>\n

\"Validation<\/p>\n

Start with a concrete action: generate a concise PowerPoint slide that shows patch adoption by device category and circulate it to the security team. Validate patch status within 24 hours of release, focusing on the largest fleets first, and keep the incident-response role aligned with safety requirements and regulatory expectations. Track installation rates across country sites and Montr \u00e9 al, then use the numbers to drive accelerated remediation when gaps appear.<\/p>\n

Patch Status Verification Checklist<\/h3>\n
    \n
  1. Confirm that the patch-management console (WSUS, Intune, SCCM, or equivalent) marks devices as Installed for the two zero-days described in the release notes; aim for rates >95% within 48 hours and >99% within 7 days, prioritizing servers, drivers, and other high-risk devices across the largest groups.<\/li>\n
  2. Cross-check Microsoft Security Update Guide details and ensure the patch bundle includes the intended fixes; verify KB numbers, affected products, and dependencies to prevent conflicts during construction of remediation plans. Also verify signatures and hashes before deployment to prevent bypass of protections.<\/li>\n
  3. Validate rollout coverage by geography and site: country-level dashboards, regional offices, and remote locations (places such as \u0440a\u0437\u043b\u0438\u0447\u043d\u044b\u0435 \u043c\u0435\u0441\u0442\u0430) to avoid gaps in complex routing topologies; ensure devices connected via VPN or satellite links receive updates; monitor rates across \u0438\u043d\u0435\u0433\u0435\u043d\u043d\u044b\u0435 and indigenous networks where control planes may differ.<\/li>\n
  4. Audit patch metadata against the device inventory: confirm machine types (laptop, desktop, server), operating systems, and driver versions align with the patch scope; ensure driver packages used for elevation fixes are the signed Microsoft binaries to prevent integrity issues.<\/li>\n
  5. Automate integrity checks: verify digital signatures, compare file hashes, and confirm that patched binaries match the release set; especially scrutinize critical drivers and system services to prevent post-patch bypass attempts.<\/li>\n
  6. Document remediation status and any failures: log root causes (offline devices, policy conflicts, or deployment blockers), assign owners, and track closure with clear timelines; export progress to a premium-level safety dashboard and share with stakeholders in Dominic\u2019s team for accountability.<\/li>\n
  7. Establish escalation thresholds: trigger accelerated remediation (\u0443\u0441\u043a\u043e\u0440\u0435\u043d\u043d\u043e\u0435) when installed-rate stall falls below a defined threshold or when telemetry shows anomalies in routing or device health; communicate first-status updates to leadership and their teams.<\/li>\n
  8. For evidence-based reporting, record metrics such as time-to-patch (TTP), success-rate by device role (workstation, server, driver-laden machines), and regional variance; use these data points to adjust protection tiers and security controls in the next release cycle.<\/li>\n
  9. Maintain a tight feedback loop with proponents of patching: share findings with safety officers, IT ops, and business units to align on risk reduction and operational impact; keep stakeholders informed with regular updates to a living document.<\/li>\n
  10. Include cross-functional checks to support travel and travel-adjacent operations (for example, \u0442\u0443\u0440\u0438\u0441\u0442\u043e\u0432 or travel teams) that rely on secure devices during shipments (\u043e\u0442\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435) and in transit; ensure elevated protections are in place for devices used in transit (\u043f\u0430\u0441\u0441\u0430\u0436\u0438\u0440\u0430) and mixed environments.<\/li>\n<\/ol>\n

    Signs of Exploitation and Detection Tactics<\/h3>\n

    \"Signs<\/p>\n

      \n
    1. Monitor for elevation and bypass indicators: unexpected privilege escalation, new or renamed administrator accounts, or unsigned binaries loading via driver paths, which may signal attempted bypass of the patch.<\/li>\n
    2. Watch for anomalous process and service activity: new services, suspicious child processes, or unusual parent-child process trees around security or system binaries; correlate with patch rollout times to distinguish legitimate updates from tampering.<\/li>\n
    3. Inspect route- and network-level signals: unexpected routing changes, anomalous DNS logs, or traffic spikes across core nodes that span Montr \u00e9 al and other sites; correlate with patch-release windows and remediation actions.<\/li>\n
    4. Look for changes in security policy and policy-related events: GPO modifications, new registry keys, or altered permission sets around critical folders and drivers; validate against baseline configurations.<\/li>\n
    5. Track unauthorized access attempts and lateral movement indicators: failed authentications from unfamiliar IPs, sudden authentication from remote locations, or new service accounts associated with high-privilege roles (driver or machine-level access).<\/li>\n
    6. Assess indicators in endpoint telemetry and SIEM alerts: spikes in EDR alerts after the release, unexpected process injections, or calls to credential dumping utilities; tag events by device, site, and user to map exposure across the fleet (across platforms and locations).<\/li>\n
    7. Correlate with supply-chain and user-behavior signals: indigenous networks or contractors\u2019 endpoints showing delayed patching or anomalous behavior; verify that only authorized devices receive patches and that exceptions are tightly controlled (\u0442\u043e\u043b\u044c\u043a\u043e controlled exceptions).<\/li>\n
    8. Conduct targeted investigations on high-risk assets first, such as those with elevated exposure in large fleets (largest devices) and those in transit or with critical roles (driver, machine); prioritize incident response playbooks accordingly.<\/li>\n
    9. Document findings and actions for after-action reviews: what was detected, how it was validated, and how the remediation was verified; maintain historical data to inform future patch cycles and to support ongoing risk management across the organization.<\/li>\n<\/ol>\n

      Medicus UAE Trial Overview: Study Design, Enrollment Milestones, and Non-Invasive BCC Therapy Mechanism<\/h2>\n

      Recommendation: Launch a country-wide UAE protocol standardization and rapid site activation to enroll 600 participants across 20 sites within 9 months. Align regulatory handling, centralized data services, and \u043a\u043b\u0438\u0435\u043d\u0442\u0430 safety procedures; deploy dermarite-based applicators to ensure consistent skin contact. Train local teams to manage handling of specimens, patient data, and adverse events across a single, unified dataset. Build a \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u0430 data flow with privy access controls, and support study visualization with visio diagrams and xaml prototypes for the UI. Use hyper-v sandboxing for patient data testing and RRAS-based secure remote access to project systems. Include samlet \u043a\u0438\u0434\u0430\u043d\u0438 details for \u0438\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u0430\u044f patient risk assessment and \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c mitigation, and ensure inclusion of \u0443\u0441\u043b\u0443\u0433\u0438 that support \u043a\u0430\u0436\u0434\u044b\u0439 \u043a\u043b\u0438\u0435\u043d\u0442\u044b across markets and industries. The departure from siloed processes and a greater emphasis on constriction-free construction of study workflows will improve turnaround times without compromising quality.<\/p>\n

      Study Design and Endpoints<\/h3>\n
        \n
      • Type and scope: multicenter, prospective, open-label, randomized (1:1) study across the country for non-invasive BCC therapy versus standard care, targeting adults with histologically confirmed basal cell carcinoma.<\/li>\n
      • Intervention: non-invasive BCC therapy mechanism employing dermarite-based applicators delivering controlled energy to affected skin while preserving surrounding tissue (skin) and minimizing downtime.<\/li>\n
      • Primary endpoint: complete response rate at 12 weeks, verified by blinded central review and high-resolution VISIO assessment tools.<\/li>\n
      • Secondary endpoints: cosmetic outcome, local recurrence at 6 and 12 months, time-to-response, patient-reported pain, and safety signals captured through a standardized handling of adverse events.<\/li>\n
      • Endpoints reliability: data captured in a dedicated subsystem with privy access controls, ensuring \u043alining data integrity and \u0432\u0435\u0440\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f of \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c mitigation measures for \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u043a\u043b\u0438\u0435\u043d\u0442\u0430. <\/li>\n
      • Data capture and tooling: study flow mapped with visio and UI prototypes built in xaml; data flows routed across secure environments via hyper-v containers and RRAS for remote site access. <\/li>\n<\/ul>\n

        Enrollment Milestones and Site Strategy<\/h3>\n
          \n
        • Initial activation: activate 20 sites (including Dubai, Abu Dhabi, and Sharjah) within 6 weeks, with standard training packages (\u0443\u0441\u043b\u0443\u0433\u0438) and local SOPs updated for \u043a\u0430\u0436\u0434\u044b\u0439 site. <\/li>\n
        • Enrollment pace: target 60 participants per month across markets, with a rollout plan to cover industries such as dermatology clinics, medical centers, and hospital outpatient services. <\/li>\n
        • Quality and resilience: implement incident management in Hyper-V environments and establish a dedicated \u6b8b\u7559 data subsystem to monitor handling, data quality, and privacy (privy) across every site. <\/li>\n
        • Milestones by quarter: 1) regulatory approvals and site initiation; 2) first patient enrolled within 4\u20136 weeks of site activation; 3) 50% enrollment by month 6; 4) full enrollment (\u2248600) by month 9; 5) 12-month follow-up completed for the last cohort. <\/li>\n
        • Localization and outreach: engage local clinicians to support \u043a\u043b\u0438\u0435\u043d\u0442\u0430 engagement, include patient education sessions, and leverage services \u0432 country-wide outreach to raise awareness in key markets. <\/li>\n
        • Risk and privacy: address \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c concerns through a robust handling protocol, with \u0438\u043d\u0434\u0438\u0432\u0438du\u0430\u043b\u044c\u043d\u0430\u044f risk assessments and controls that protect client data (\u043a\u043b\u0438\u0435\u043d\u0442\u0430) and maintain \u0434\u043e\u0432\u0435\u0440\u0438e across the country (country). <\/li>\n
        • Departure from legacy approaches: replace fragmented data collection with a single, integrated system across sites, leveraging visio-driven study maps and xaml-based interfaces to reduce delays and improve site readiness. <\/li>\n<\/ul>\n

          Outlook for Medicus: Regulatory Milestones, Patient Access, and Study Adoption in the Region<\/h2>\n

          Coordinate regulatory milestones with patient-access programs now to accelerate regional study adoption for Medicus; align montr\u00e9al and international markets through some major updates, streamlined procedures, and \u0438\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u0430\u044f care paths. This approach drives faster enrolment, improves patient experience, and supports payer conversations without compromising safety. Leverage win32k and xaml integrations to deliver fast forms and updates to care teams, while maintaining strict controls and bypass risk management. Also, foster \u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u0435 for sites and patients to reduce \u043f\u043e\u0441\u0430\u0434\u043a\u0443 into trials and to improve the passenger experience for \u043f\u0430\u0441\u0441\u0430\u0436\u0438\u0440\u0430 journeys.<\/p>\n\n\n\n\n\n\n\n\n
          Market \/ Region<\/th>\nMilestone<\/th>\nTarget Date<\/th>\nStatus<\/th>\nNotas<\/th>\n<\/tr>\n<\/thead>\n
          Montr\u00e9al, Canada<\/td>\nRegulatory Submission<\/td>\nQ4 2025<\/td>\nPlanned<\/td>\naligns with local \u0444\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u0435\u0439; updates in patient-facing collateral<\/td>\n<\/tr>\n
          International Markets<\/td>\nPricing & Reimbursement Negotiations<\/td>\nH2 2026<\/td>\nPlanned<\/td>\nupdates to coverage; supports care access across markets<\/td>\n<\/tr>\n
          Regional Study Adoption<\/td>\nStudy Onboarding for Sites<\/td>\nQ1 2026<\/td>\nIn Progress<\/td>\n\u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u0435 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u043f\u043e\u0440\u0442\u0430\u043b\u0430 \u043a\u043b\u0438\u0435\u043d\u0442\u0430; faster onboarding<\/td>\n<\/tr>\n
          Care Programs<\/td>\nPatient Access Pathways<\/td>\nQ3 2025<\/td>\nCompleted<\/td>\n\u0438\u043d\u0434\u0438\u0432\u0438\u0434\u0443\u0430\u043b\u044c\u043d\u0430\u044f care; \u043f\u0430\u0441\u0441\u0430\u0436\u0438\u0440\u0430 experience improvements<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          Regulatory Milestones<\/h3>\n

          In Montr\u00e9al, complete the regulatory package by Q4 2025 and file amendments in early 2026 to reflect updated study designs and safety monitoring plans. Target two major milestones in 2026: formal approvals for three regional sites and a companion submission for payer coverage in two key markets. Maintain a dedicated projects team to track updates<\/em> to guidelines, and use client-facing dashboards to communicate progress. Expect extended review cycles where necessary, but keep formalities tight with pre-submission checks and controlled bypass risk across all inputs. Leverage Xbox-enabled demonstration labs and related testing environments to validate care workflows end-to-end, and document all changes in a single, auditable yard<\/em> of records.<\/p>\n

          Study Adoption and Patient Access<\/h3>\n

          Advance patient access through centralized onboarding, consent, and retention programs that align with regional care expectations. Target a 25\u201340% improvement in onboarding time across Montr\u00e9 al and international sites, with enrollment rates rising through dedicated \u0441\u043e\u043f\u0440\u043e\u0432\u043e\u0436\u0434\u0435\u043d\u0438\u0435. Use rapid updates<\/em> to patient-facing portals and forms (without compromising privacy) to reduce frictions at the point of care. Maintain a fast feedback loop from investigators and sites to refine procedures, pathways, and materials, and track performance by market with monthly dashboards that show participation rates, drop-off points, and overall experience improvements for both patients and staff.<\/p>","protected":false},"excerpt":{"rendered":"

          Apply the updates now to neutralize the two zero-day vulnerabilities and the 81 fixes released this Patch Tuesday. Quick deployment minimizes exposure across devices, and reduces the risk of exploitation that can spread like sepsis through an unpatched environment. first\u2013the two zero-day vulnerabilities pose high risk with potential for remote code execution, privilege escalation, and […]<\/p>","protected":false},"author":2,"featured_media":3892,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"fifu_image_url":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","fifu_image_alt":"","footnotes":""},"categories":[],"tags":[],"class_list":["post-3890","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"acf":[],"yoast_head":"\nMicrosoft Patch Tuesday Two zero-day flaws and 81 fixes<\/title>\n<meta name=\"description\" content=\"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Microsoft Patch Tuesday Two zero-day flaws and 81 fixes\" \/>\n<meta property=\"og:description\" content=\"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/\" \/>\n<meta property=\"og:site_name\" content=\"Istanbul International Airport (IST) - Turkey's new airport\" \/>\n<meta property=\"article:published_time\" content=\"2025-09-17T04:06:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\" \/>\n<meta name=\"author\" content=\"anastasia_maisuradze\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"anastasia_maisuradze\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/\"},\"author\":{\"name\":\"anastasia_maisuradze\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/#\\\/schema\\\/person\\\/71ece384d901a99eb7f9197b612d8a26\"},\"headline\":\"Microsoft September Patch Tuesday – Two Zero-Day Vulnerabilities and 81 Bugs Fixed\",\"datePublished\":\"2025-09-17T04:06:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/\"},\"wordCount\":2792,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/wp-content\\\/images\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\",\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/\",\"url\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/\",\"name\":\"Microsoft Patch Tuesday Two zero-day flaws and 81 fixes\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/wp-content\\\/images\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\",\"datePublished\":\"2025-09-17T04:06:53+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/#\\\/schema\\\/person\\\/71ece384d901a99eb7f9197b612d8a26\"},\"description\":\"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#primaryimage\",\"url\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/wp-content\\\/images\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\",\"contentUrl\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/wp-content\\\/images\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Travel Guide\",\"item\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Microsoft September Patch Tuesday – Two Zero-Day Vulnerabilities and 81 Bugs Fixed\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/#website\",\"url\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/\",\"name\":\"Istanbul International Airport (IST) - Turkey's new airport\",\"description\":\"Navigating Istanbul International Airport: A Traveler\u2019s Guide.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/#\\\/schema\\\/person\\\/71ece384d901a99eb7f9197b612d8a26\",\"name\":\"anastasia_maisuradze\",\"url\":\"https:\\\/\\\/istanbul-ist-international-airport.com\\\/pt\\\/author\\\/anastasia_maisuradze\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Microsoft Patch Tuesday Two zero-day flaws and 81 fixes","description":"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/","og_locale":"pt_PT","og_type":"article","og_title":"Microsoft Patch Tuesday Two zero-day flaws and 81 fixes","og_description":"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.","og_url":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/","og_site_name":"Istanbul International Airport (IST) - Turkey's new airport","article_published_time":"2025-09-17T04:06:53+00:00","og_image":[{"url":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","type":"","width":"","height":""}],"author":"anastasia_maisuradze","twitter_card":"summary_large_image","twitter_image":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","twitter_misc":{"Escrito por":"anastasia_maisuradze","Tempo estimado de leitura":"14 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#article","isPartOf":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/"},"author":{"name":"anastasia_maisuradze","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/#\/schema\/person\/71ece384d901a99eb7f9197b612d8a26"},"headline":"Microsoft September Patch Tuesday – Two Zero-Day Vulnerabilities and 81 Bugs Fixed","datePublished":"2025-09-17T04:06:53+00:00","mainEntityOfPage":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/"},"wordCount":2792,"commentCount":0,"image":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#primaryimage"},"thumbnailUrl":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","inLanguage":"pt-PT","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/","url":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/","name":"Microsoft Patch Tuesday Two zero-day flaws and 81 fixes","isPartOf":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/#website"},"primaryImageOfPage":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#primaryimage"},"image":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#primaryimage"},"thumbnailUrl":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","datePublished":"2025-09-17T04:06:53+00:00","author":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/#\/schema\/person\/71ece384d901a99eb7f9197b612d8a26"},"description":"Microsoft September Patch Tuesday covers two zero-day vulnerabilities and 81 fixes, outlining affected products and the security implications for Windows, Office, and enterprise deployments.","breadcrumb":{"@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/"]}]},{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#primaryimage","url":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","contentUrl":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-bugs-fixed\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/istanbul-ist-international-airport.com\/"},{"@type":"ListItem","position":2,"name":"Travel Guide","item":"https:\/\/istanbul-ist-international-airport.com\/pt\/blog\/"},{"@type":"ListItem","position":3,"name":"Microsoft September Patch Tuesday – Two Zero-Day Vulnerabilities and 81 Bugs Fixed"}]},{"@type":"WebSite","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/#website","url":"https:\/\/istanbul-ist-international-airport.com\/pt\/","name":"Istanbul International Airport (IST) - Turkey's new airport","description":"Navigating Istanbul International Airport: A Traveler\u2019s Guide.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/istanbul-ist-international-airport.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Person","@id":"https:\/\/istanbul-ist-international-airport.com\/pt\/#\/schema\/person\/71ece384d901a99eb7f9197b612d8a26","name":"anastasia_maisuradze","url":"https:\/\/istanbul-ist-international-airport.com\/pt\/author\/anastasia_maisuradze\/"}]}},"views":153,"fifu_image_url":"https:\/\/istanbul-ist-international-airport.com\/wp-content\/images\/microsoft-september-patch-tuesday-two-zero-day-vulnerabilities-and-81-.jpg","_links":{"self":[{"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/posts\/3890","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/comments?post=3890"}],"version-history":[{"count":0,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/posts\/3890\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/media\/3892"}],"wp:attachment":[{"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/media?parent=3890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/categories?post=3890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/istanbul-ist-international-airport.com\/pt\/wp-json\/wp\/v2\/tags?post=3890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}