The Apache CXF fork 3.5.11.SP branch latest tag isn't used yet, but should be consumed by upcoming JBoss EAP 7.4.24, while the latest released JBoss EAP 7.4.23 consumes JBossWS CXF 5.4.15.Final-redhat-00001 and Apache CXF 3.5.10-redhat-00001.
For JBoss EAP, consuming the next tag of the JBossWS CXF maintenance branch, i.e. jbossws-cxf-5.4.x, would include several bugfixes which have been backported there, e.g.: JBWS-4445 , JBWS-4450 , JBWS-4451 , JBWS-4452 and JBWS-4453

As a good practice, such forked Apache CXF tag should be consumed by JBossWS CXF, too, therefore the JBossWS CXF maintenance branch should be updated to use the productized version of tag cxf-3.5.11-jbossorg-2 from forked Apache CXF 3.5.11, i.e. the latest tag in the 3.5.11.SP branch.

It should be then tested (i.e. whole testsuite run, ideally against JBoss EAP 7.4.x topic branch) and - if results are green - it should be finally consolidated into a jbossws-cxf-5.4.18.Final tag, for it to be productized and consumed by JBoss EAP 7.4.24 to, instead of 5.4.15.Final-redhat-00001.