In late September I published a release of compose-lint , a security linter for Docker Compose files that I maintain. It fixed two vulnerabilities , and I published the advisories about fifteen minutes later. GitHub reviewed them 44 days after that, and until then no scanner that relies on GitHub's advisory data could tell anyone running an affected version that a fix existed. I wanted to know how typical that was, so I pulled the data.
If you run a vulnerability management program, the clock for a finding starts when your scanner reports it, and a scanner can only report what's in the vulnerability data it reads. That's true for any kind of software. I measured the gap for open source packages, where the dates are public, using one of the main sources, the GitHub Advisory Database. For fixes released this summer, the typical advisory was reviewed into it about four weeks after the fixed version was published, and six weeks in the worst month.
Median days after the fixed version was released.…