The vulnerability lies in the graphql-ws protocol handler in strawberry-graphql. The analysis of the provided patch 0977a4e6b41b7cfe3e9d8ba84a43458a2b0c54c2 shows that the handle_start method within the GraphQLWSHandler class in strawberry/subscriptions/protocols/graphql_ws/handlers.py was modified. A check was added to ensure that a connection_init message was processed before allowing a subscription to be created. Specifically, a connection_acknowledged flag is now checked at the beginning of handle_start. If this flag is False, the connection is closed with an 'Unauthorized' error. Before this change, an attacker could send a start message over a WebSocket connection using the graphql-ws subprotocol without sending a connection_init message first. This would bypass any authentication logic implemented in the on_ws_connect handler, leading to an authentication bypass.