Our engineers reproduced the issue in a non-production environment, and have determined that this incident was caused by a known bug in one of the software libraries used by our web servers. We will be updating our web server software after testing in the coming weeks.