While your point stands - it's worth pointing out that this bug was NOT caused by an update [1], but seems to have been a long-standing bug in the HTTP3 stack that was triggered due to some external site (including apparently Mozilla's telemetry provider) that changed their stack.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1749908