# Spring4Shell ::Spring Framework Remote Code Execution Vulnerability for eck operator

**URL:** <https://discuss.elastic.co/t/spring4shell-spring-framework-remote-code-execution-vulnerability-for-eck-operator/302455>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [April 14, 2022, 4:31pm UTC](https://discuss.elastic.co/t/spring4shell-spring-framework-remote-code-execution-vulnerability-for-eck-operator/302455 "2022-04-14T16:31:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sagarika\_Mahalik](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@Sagarika\_Mahalik](https://discuss.elastic.co/u/Sagarika_Mahalik)\
**Post date:** [April 14, 2022, 4:31pm UTC](https://discuss.elastic.co/t/spring4shell-spring-framework-remote-code-execution-vulnerability-for-eck-operator/302455/1 "2022-04-14T16:31:48Z")

</div>

Hello,

We are using eck operator 1.9.1.  
I see the code for eck operator is written on go lang. So then is eck operator not affected any way by the reported spring shell vulnerability?

Please suggest, whether we need to take any steps from our end for mitigating the same

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 12, 2022, 4:32pm UTC](https://discuss.elastic.co/t/spring4shell-spring-framework-remote-code-execution-vulnerability-for-eck-operator/302455/2 "2022-05-12T16:32:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.