Use of a Broken or Risky Cryptographic Algorithm Affecting eap8-activemq-artemis-dto package, versions <0:2.40.0-6.redhat_00012.1.el9eap


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-EAP8ACTIVEMQARTEMISDTO-16759092
  • published19 May 2026
  • disclosed15 Apr 2026

Introduced: 15 Apr 2026

CVE-2025-14813  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:9 eap8-activemq-artemis-dto to version 0:2.40.0-6.redhat_00012.1.el9eap or higher.
This issue was patched in RHSA-2026:18055.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap8-activemq-artemis-dto package and not the eap8-activemq-artemis-dto package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

: Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (core modules).

This vulnerability is associated with program files G3413CTRBlockCipher.

This issue affects BC-JAVA: from 1.59 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.

CVSS Base Scores

version 3.1