Patch & vulnerability status
git-age 0.2.1
Latest tracked version 0.2.1. Release status, tracked CVEs, and automated cross-platform patching for git-age.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 0.2.1 | 0 | 2024-12-06 |
Why keeping git-age patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every git-age release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches git-age
Lavawall® watches git-age releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on git-age, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks git-age at version 0.2.1 (last checked 2024-12-06). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall continuously monitors git-age for newly disclosed CVEs and remediates them automatically as they appear.
Deploy the Lavawall® agent and git-age updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for git-age through public information and proprietary statistical analysis, and can patch it automatically across your fleet.