This article helps to explain if Erlang/OTP ssh vulnerability (CVE-2025-32433) has any impact on Paragon Automation application.

As per internal checks, Paragon Automation deployment of rabbitMQ container doesn’t have ssh library.. We did regress testing and QA did validate in QA lab by Engg team ..

Paragon Team just deploy rabbitmq as a third party container, meaning we don’t build it we just use what is available form rabbitmq developers.

rabbitmq-1:/opt/bitnami/erlang$ lib/erlang/bin/erl

Erlang/OTP 26 [erts-14.0.2] [source] [64-bit] [smp:14:14] [ds:14:14:10] [async-threads:1] [jit:ns]

Eshell V14.0.2 (press Ctrl+G to abort, type help(). for help)

1> application:which_applications().

[{stdlib,"ERTS CXC 138 10","5.0.2"},

{kernel,"ERTS CXC 138 10","9.0.2"}]

2> ssh:start().

** exception error: undefined function ssh:start/0

3>

As we can see it isn’t included in the container we are using.

No Impact of Erlang/OTP ssh vulnerability (CVE-2025-32433) on Paragon Automation application.