Automatically patch vulnerable packages
Kristján Oddsson
This guide shows you how to create a Vulnerability Patching policy so that vulnerable packages across your fleet are upgraded automatically. You need access to the Workbrew Console with permission to write Policies.
Create a Vulnerability Patching policy
- Navigate to the Policies page in the Workbrew Console
- Click New Brew Policy
- Select Vulnerability Patching
- Set a minimum severity for Vulnerable formulae
- Set a minimum severity for Vulnerable casks
- Click the Device Group dropdown to target a Device Group, or leave it as All Devices
- Click Enable Vulnerability Patching
Both package types start at Off, so set at least one of them to a severity. A policy saved with both left Off is created but patches nothing.
Each Device Group can only have one Vulnerability Patching policy, and a policy targeting All Devices counts as one too. The severity levels and the CVSS scores behind them are listed in Package vulnerabilities.
Confirm the policy is active
The policy appears on the Policies page with a badge for each package type showing the threshold you chose, for example "Formulae ≥ High" and "Casks Off". The All threshold shows as "All updates".
Patching runs when a Device next checks in, not when you save the policy, so give the fleet a check-in cycle before expecting the Vulnerabilities page to change.
Update or remove the policy
- Navigate to the Policies page
- Click the Vulnerability Patching policy you want to change
- Adjust the thresholds or Device Group and click Save changes, or click Remove Vulnerability Patching
Removing the policy stops future patching. It does not roll back packages that have already been upgraded.
Related docs
- Package vulnerabilities - severity levels, CVSS cutoffs, and every Vulnerability Patching option
- How vulnerability patching works - when patching runs and what qualifies a package for it
- Declare policies to block software packages - block forbidden formulae, casks, and licenses
- How policies apply to devices in multiple groups - policy precedence when a Device is in several groups
- Preserve app settings during cask upgrades - keep app data intact when casks upgrade in place
- Getting started with Workbrew - Workspace setup and Device onboarding