Comment by GabrielBianconi

2 days ago

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

0 comments