Currently, the camunda-parent manages the versions for some Spring artifacts (see here: https://github.com/camunda/camunda-bpm-platform/blob/master/parent/pom.xml#L282). Those versions differ from the versions necessary for Spring Boot-based projects.
The Camunda Spring Boot Starter and Camunda BPM Run therefore do not use that parent but the camunda-root. This works but somehow introduces minimal overhead for the POMs of those projects since they need to copy-paste some properties and profiles the camunda-parent usually provides.
More severely, this influences the Camunda BPM Run EE, because its parent camunda-root-ee is based on camunda-database-settings which inherits from the camunda-parent. Therefore, the webapps module in Run EE might be influenced by those managed versions of the parent. Currently, the build works because only spring-web-mvc is pulled in as a Spring artifact and this is not managed by the camunda-parent. This is however very prone to break in the future.
Extract the managed versions of the Spring artifacts from the camunda-parent either into a new parent for the modules that need them or, if only engine-spring needs them, move those versions there.