Quarkus 3.15.3 intoduces a new filter io.quarkus.devui.runtime.LocalHostOnlyFilter that bans the access to the Dev UI, for whatever origin distinct from localhost,  independently of the cors configuration.
 
That introduces the following impact in workflows with dev profile deployments:
 
In OSL 1.35.0, (quarkus 3.8.6) we configured these workflows with the following example properties, and the dev-ui worked fine. 
 

quarkus.http.cors = true quarkus.http.cors.origins = https://greet2-test.apps-crc.testing

 
With the code in main (upcoming 1.36.0, quarkus 3.15.3), that configuration is banned by the given filter.
 
We must investigate if there are any new configurations to bypass that filter,, etc. And apply them to make the dev-ui work in the OSL 1.36.0.
 
If such configuration don't exists, we must look for an alternative solution if any.