13 matches found
Azure File Sync Agent v22.3 Release – April 2026 (KB5087090)
Azure File Sync Agent v22.3 Release – April 2026 KB5087090...
Azure File Sync Agent v22.3 Release – April 2026 (KB5087090)
Azure File Sync Agent v22.3 Release – April 2026 KB5087090...
Azure File Sync Agent v22.1 Release – February 2026 (KB5080681)
Update Rollup for Azure File Sync agent version 22.1.0.0. For more details, see the associated Microsoft Knowledge Base article...
Security Updates for Azure File Sync Agent (August 2025)
The Microsoft Azure File Sync Agent running on the remote host is prior to 18.3, 19.x prior to 19.2, 20.x prior to 20.1, or 21.x prior to 21.1. It is, therefore affected by an elevation of privilege vulnerability. Note that Nessus has not tested for this issue but has instead relied only on the...
Azure File Sync Agent v21.1 Release – August 2025 (KB5063486)
Security Update for Azure File Sync agent version 21.1.0.0. For more details, see the associated Microsoft Knowledge Base article...
Azure File Sync Agent v20.0 Release – February 2025 (KB5041884)
Update Rollup for Azure File Sync agent version 20.0.0.0. For more details, see the associated Microsoft Knowledge Base article...
Azure File Sync Agent v20.0 Release – February 2025 (KB5041884)
Update Rollup for Azure File Sync agent version 20.0.0.0. For more details, see the associated Microsoft Knowledge Base article...
Security Updates for Azure File Sync Agent (June 2024)
The Microsoft Azure File Sync Agent running on the remote host is 17.0 prior to 17.3 or 18.0 prior to 18.1. It is, therefore affected by an elevation of privilege vulnerability. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version...
Azure File Sync Agent v18.1 Release - June 2024 (Security-only update)
None None...
Azure File Sync Agent v16.2 Release - February 2024 (Security-only update)
None None...
Security Updates for Azure File Sync Agent (February 2024)
The Microsoft Azure File Sync Agent running on the remote host is 16.0 prior to 16.2 or 17.0 prior to 17.1. It is, therefore affected by an elevation of privilege vulnerability. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version...