Yes. io.quarkus:quarkus-csrf-reactive (Maven): upgrade to 2.16.11.Final or later; io.quarkus:quarkus-keycloak-authorization (Maven): upgrade to 2.16.11.Final or later; io.quarkus:quarkus-undertow (Maven): upgrade to 2.16.11.Final or later; io.quarkus:quarkus-vertx-http (Maven): upgrade to 2.16.11.Final or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-4853?
Check whether you run io.quarkus:quarkus-csrf-reactive (Maven), io.quarkus:quarkus-keycloak-authorization (Maven), io.quarkus:quarkus-undertow (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
io.quarkus:quarkus-csrf-reactive (Maven): upgrade to 2.16.11.Final or later
# set io.quarkus:quarkus-csrf-reactive to 2.16.11.Final in your pom.xml or build.gradle
io.quarkus:quarkus-keycloak-authorization (Maven): upgrade to 2.16.11.Final or later
# set io.quarkus:quarkus-keycloak-authorization to 2.16.11.Final in your pom.xml or build.gradle
io.quarkus:quarkus-undertow (Maven): upgrade to 2.16.11.Final or later
# set io.quarkus:quarkus-undertow to 2.16.11.Final in your pom.xml or build.gradle
io.quarkus:quarkus-vertx-http (Maven): upgrade to 2.16.11.Final or later
# set io.quarkus:quarkus-vertx-http to 2.16.11.Final in your pom.xml or build.gradle