The implementation of several functions in the @fastly/js-compute package includes a use-after-free bug. This bug could allow for unintended data loss if the result of the preceding functions were sent anywhere else, and often results in a Compute service crash causing an HTTP 500 error to be returned. The affected functions include `FetchEvent.client.tlsCipherOpensslName`, `FetchEvent.client.tlsProtocol`, `FetchEvent.client.tlsClientCertificate`, `FetchEvent.client.tlsJA3MD5`, `FetchEvent.client.tlsClientHello`, `CacheEntry.prototype.userMetadata` of the `fastly:cache` subsystem, and `Device.lookup` of the `fastly:device` subsystem. As all requests to Compute are isolated from one another, the only data at risk is data present for a single request.