[BUG][JAVA] Coverity giving High risk severity issue in ApiClient code - Filesystem path, filename, or URI manipulation

Description

Coverity code analysis tool is raising the security issue of type Filesystem path, filename, or URI manipulation in the ApiClient code.

3. Calling "deserialize". This call uses "response" for sensitive computation. (The virtual call resolves to "client.api.ApiClient.deserialize(jakarta.ws.rs.core.Response, jakarta.ws.rs.core.GenericType)".)

Impacted code

public <T> ApiResponse<T> invokeAPI(...) {
    [...]

    if (statusCode == Status.NO_CONTENT.getStatusCode()) {
        return new ApiResponse<T>(statusCode, responseHeaders);
    } else if (response.getStatusInfo().getFamily() == Status.Family.SUCCESSFUL) {
        if (returnType == null) {
            return new ApiResponse<T>(statusCode, responseHeaders);
        } else {
            return new ApiResponse<T>(statusCode, responseHeaders, deserialize(response, returnType));
        }
    } else {
    
    [...]
}

The issue is raised on this specific line :

return new ApiResponse<T>(statusCode, responseHeaders, deserialize(response, returnType));

Is there any way to fix or to avoid this issue ?

openapi-generator version

openapi-generator-maven-plugin, version 6.6.0

Generation Details

Java generator, using jersey3 as library

Start by tracing the Java jersey3 ApiClient.invokeAPI path around the deserialize(response, returnType) call and review how Coverity interprets that flow. Reproduce the finding with openapi-generator-maven-plugin version 6.6.0, then validate that the generated client still behaves correctly and the reported filesystem path, filename, or URI manipulation issue is resolved or appropriately addressed.