You can try this workaround :

cd ./domain/old/images/images2010/news/
mv 53x53_*ancejevonku.jpg normal_name.jpg

Proceed with your workflow.
When required , you can rename that back to something like the original.

(1) Workaround :

You can try this :

cd ./domain/old/images/images2010/news/
mv 53x53_*ancejevonku.jpg normal_name.jpg

Proceed with your workflow.
When required , you can rename that back to something like the original.

(2) Solution :

I am not very clear what your Issue is or what you want to achieve.
The way I am interpreting your Situation , this Solution will work :
On the Original Directory, top-level of the back-up , you can make a zip (or tar) file of the whole Directory.
Then back-up this zip (or tar) file to you cifs volume. The weird filename will then be hidden inside that container , hence the workflow will not encounter the Current Issue.
When necessary , you can unzip to the original Directory where the weird filename will come out to be visible , but there is no Access Issue on the workflow there.

You can try this workaround :

CD ./domain/old/images/images2010/news/
mv 53x53_*ancejevonku.jpg normal_name.jpg

Proceed with your workflow.
When required , you can rename that back to something like the original.

You can try this workaround :

cd ./domain/old/images/images2010/news/
mv 53x53_*ancejevonku.jpg normal_name.jpg

Proceed with your workflow.
When required , you can rename that back to something like the original.