Automating patches does not require paying for licenses. Open-source tools can keep anything from a handful of servers to thousands of Linux machines up to date, and they cover a good share of Windows applications too. This guide walks through the free options sysadmins use most, from simplest to most complete, with example commands, and explains when a commercial product starts to make sense.

Key points on open-source patching in 20 seconds

  • unattended-upgrades and dnf-automatic handle basic security patching on Debian and RHEL.
  • Ansible and Salt orchestrate batched updates and reboots across many servers.
  • Foreman with Katello and Uyuni add local repositories and test environments.
  • winget and Chocolatey update third-party apps on Windows.

Spanish security site opensecurity.es has published a 2026 guide to patch management tools (in Spanish) that compares free and commercial options from a security standpoint. Here we focus on the practical side: how to get started with each one. The urgency is real. According to Microsoft’s 2026 Digital Defense Report, the median time from vulnerability discovery to weaponization is now well under 24 hours, and this year will close with around 72,000 catalogued vulnerabilities.

Level 1: native automatic updates

For standalone servers, or as a safety net, distributions ship tools that install security updates on their own. On Debian and Ubuntu that is unattended-upgrades:

sudo apt install unattended-upgrades apt-listchanges
sudo dpkg-reconfigure -plow unattended-upgrades

# See what it would do without installing anything
sudo unattended-upgrade --dry-run --debugCode language: PHP (php)

Its settings live in /etc/apt/apt.conf.d/50unattended-upgrades, where you choose the allowed origins (security only by default), package blocklists, email reports, and whether and when automatic reboots are allowed. On Red Hat, Rocky Linux, AlmaLinux and related distributions, the equivalent is dnf-automatic:

sudo dnf install dnf-automatic
# In /etc/dnf/automatic.conf: upgrade_type = security and apply_updates = yes
sudo systemctl enable --now dnf-automatic.timer
systemctl list-timers dnf-automatic.timerCode language: PHP (php)

These tools are reliable but give you no central view: there is no console showing which servers are current and which are not. Once you have more than a few machines, you need the next level.

Level 2: orchestration with Ansible or Salt

Ansible is agentless: it connects over SSH (or WinRM on Windows) and runs YAML playbooks. A minimal playbook that updates servers from different families in batches of five, rebooting only when needed, looks like this:

- hosts: servers
  become: true
  serial: 5
  tasks:
    - name: Upgrade packages on Debian and Ubuntu
      ansible.builtin.apt:
        upgrade: dist
        update_cache: true
      when: ansible_os_family == "Debian"

    - name: Upgrade packages on the Red Hat family
      ansible.builtin.dnf:
        name: "*"
        state: latest
      when: ansible_os_family == "RedHat"

    - name: Check whether Debian requests a reboot
      ansible.builtin.stat:
        path: /var/run/reboot-required
      register: reboot_flag

    - name: Reboot if required
      ansible.builtin.reboot:
      when: reboot_flag.stat.existsCode language: JavaScript (javascript)

Run it with ansible-playbook -i inventory.ini patch.yml, and test it first with --check and against a small group of servers. The serial directive matters: it stops you from rebooting a whole cluster at once.

Salt uses an agent (minion) on each machine connected to a master, which makes it very fast on large fleets. Listing and applying updates is as simple as:

# Pending packages on every minion
sudo salt '*' pkg.list_upgrades

# Upgrade only the web servers, 10 at a time
sudo salt -b 10 'web*' pkg.upgradeCode language: PHP (php)

If you already run Puppet, you can stay on OpenVox, the community fork created after Perforce moved new Puppet binaries to a private repository in 2025. It remains compatible with existing modules. For inventory and compliance views on top of all this, Rudder and Fleet are open-source options worth a look.

Level 3: your own repositories with Foreman, Katello or Uyuni

Orchestration alone is not enough if every server pulls straight from public repositories: a patch published mid-week reaches production untested. Foreman with Katello fixes that by syncing repositories to a local server and organizing them into content views and lifecycle environments (for example development, testing and production). A patch lands in testing first and is promoted to production once validated. Katello also shows pending security errata per server, which gives you the central visibility that was missing.

Uyuni, the community project behind SUSE’s commercial Linux management product, offers something similar built on Salt: software channels, scheduled patching, CVE-based vulnerability audits and support for SUSE, openSUSE, Red Hat-family distributions, Debian and Ubuntu. Both can patch air-gapped networks without direct internet access, a common situation in industrial or regulated environments.

Windows with free tools, and when to go commercial

On Windows, the operating system is usually patched with Windows Update, Intune or WSUS, which is free but was deprecated by Microsoft in 2024. For third-party applications, a constant source of vulnerabilities, the open-source package managers winget and Chocolatey can update them from the command line or a scheduled task:

winget upgrade
winget upgrade --all --silent --accept-package-agreements --accept-source-agreements

choco outdated
choco upgrade all -y

You can trigger these from Ansible using its Windows modules, managing Linux and Windows with the same tool. Commercial products start to pay off when you have many remote endpoints, a small team or compliance reporting requirements. SaaS platforms such as NinjaOne or Automox reach laptops off the corporate network without a VPN; ManageEngine, HCL BigFix or Ivanti bring catalogs of hundreds of pre-packaged applications and prioritization based on real-world exploitation; and Jamf is the standard for Macs.

Whatever you choose, three habits prevent nasty surprises: always test on a small group before a wide rollout, prioritize vulnerabilities listed in CISA’s KEV catalog or with a high EPSS score, and lock down the management server with strong authentication, because whoever controls it can run code on every machine.

FAQ

How do I enable automatic security updates on Ubuntu?

Install unattended-upgrades and run sudo dpkg-reconfigure -plow unattended-upgrades; settings live in /etc/apt/apt.conf.d/50unattended-upgrades.

Ansible or Salt for server patching?

Ansible is easier to start with because it is agentless; Salt is faster on very large fleets thanks to its agents and event bus.

How can I test patches before production?

Use local repositories and lifecycle environments, such as those in Foreman with Katello or Uyuni, or apply patches to a small group of servers first.

Sources:

Scroll to Top