Missing Authentication for Critical Function Affecting log4j:2/log4j-slf4j package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.33% (25th 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 IDSNYK-RHEL8-LOG4J-17754487
  • published1 Jul 2026
  • disclosed1 Jun 2026

Introduced: 1 Jun 2026

CVE-2026-49270  (opens in a new tab)
CWE-306  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 log4j:2/log4j-slf4j.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j:2/log4j-slf4j package and not the log4j:2/log4j-slf4j package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All.

Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6.

Users are recommended to upgrade to version 6.2.6 or 5.19.7, which fixes the issue.

CVSS Base Scores

version 3.1