CVE-2026-34477

In summary:

The fix for CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName attribute of the <Ssl> element. Although the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.

A network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:

• An SMTP, Socket, or Syslog appender is in use.
• TLS is configured via a nested <Ssl> element.
• The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.

This issue does not affect users of the HTTP appender, which uses a separate verifyHostname attribute that was not subject to this bug and verifies host names by default. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

National Vulnerability Database (CVE-2026-34477)

After review, it has been determined that Cascade Cloud environments are not affected by CVE-2026-34477, as the attack vector relies on an implementation of Log4j that is not utilized in the application. Similarly, for on-premise Cascade CMS environments, the default configuration shipped with Cascade CMS is not affected.