Comment by GabrielBianconi

This was coincidental. Someone reported the issue last week, we fixed it, and published the advisory.