CVE-2025-68161

The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName configuration attribute or the log4j2.sslVerifyHostName system property is set to true.

This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:

• The attacker is able to intercept or redirect network traffic between the client and the log receiver.
• The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).

Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.

As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.

Red Hat Lightwell has released org.apache.logging.log4j:log4j-1.2-api 2.24.3.rhlw-00004 with backported fixes for CVE-2025-68161, CVE-2026-34477, CVE-2026-34478, and CVE-2026-34480.

CVE-2025-68161: Apache Log4j Core: Missing TLS hostname verification in Socket appender

CVE-2026-34477: Apache Log4j Core: verifyHostName attribute silently ignored in TLS configuration, allowing hostname verification bypass

CVE-2026-34478: Apache Log4j Core: Log injection in Rfc5424Layout due to silent configuration incompatibility

CVE-2026-34480: Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

This patched artifact is a drop-in replacement for org.apache.logging.log4j:log4j-1.2-api 2.24.3 from Maven Central.

Red Hat Lightwell has released org.apache.logging.log4j:log4j-core 2.24.3.rhlw-00004 with backported fixes for CVE-2025-68161, CVE-2026-34477, CVE-2026-34478, and CVE-2026-34480.

CVE-2025-68161: Apache Log4j Core: Missing TLS hostname verification in Socket appender

CVE-2026-34477: Apache Log4j Core: verifyHostName attribute silently ignored in TLS configuration, allowing hostname verification bypass

CVE-2026-34478: Apache Log4j Core: Log injection in Rfc5424Layout due to silent configuration incompatibility

CVE-2026-34480: Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

This patched artifact is a drop-in replacement for org.apache.logging.log4j:log4j-core 2.24.3 from Maven Central.

Root has patched CVE-2025-68161 in the org.apache.logging.log4j:log4j-core package for Root:Maven. Multiple fixed versions available.

The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.

TuxCare rebuilt org.apache.logging.log4j:log4j-core to address 1 CVE. Fixed in 2.17.1-tuxcare.1.

TuxCare rebuilt org.apache.logging.log4j:log4j-core to address 1 CVE. Fixed in 2.22.1-tuxcare.2.

TuxCare rebuilt 2 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.24.3-tuxcare.1.

TuxCare rebuilt 2 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.18.0-tuxcare.1.

TuxCare rebuilt 2 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.17.2-tuxcare.2.

TuxCare rebuilt 3 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.19.0-tuxcare.1.

TuxCare rebuilt org.apache.logging.log4j:log4j-core to address 3 CVEs. Fixed in 2.23.1-tuxcare.2.

TuxCare rebuilt org.apache.logging.log4j:log4j-core to address 1 CVE. Fixed in 2.13.3-tuxcare.2.

TuxCare rebuilt 4 org.apache.logging.log4j packages to address 5 CVEs. Fixed in 2.20.0-tuxcare.2.

TuxCare rebuilt 4 org.apache.logging.log4j packages to address 4 CVEs. Fixed in 2.21.1-tuxcare.1.

TuxCare rebuilt 3 org.apache.logging.log4j packages to address 5 CVEs. Fixed in 2.25.2-tuxcare.1.

These are all security issues fixed in the log4j-2.20.0-1.1 package on the GA media of openSUSE Tumbleweed.

This update for coredns fixes the following issues:

Changes in coredns:

• fix CVE-2025-68156 bsc#1255345

• fix CVE-2025-68161 bsc#1256411

• Update to version 1.14.0:

  • core: Fix gosec G115 integer overflow warnings
  • core: Add regex length limit
  • plugin/azure: Fix slice init length
  • plugin/errors: Add optional show_first flag to consolidate directive
  • plugin/file: Fix for misleading SOA parser warnings
  • plugin/kubernetes: Rate limits to api server
  • plugin/metrics: Implement plugin chain tracking
  • plugin/sign: Report parser err before missing SOA
  • build(deps): bump github.com/expr-lang/expr from 1.17.6 to 1.17.7

• Update to version 1.13.2:

  • core: Add basic support for DoH3
  • core: Avoid proxy unnecessary alloc in Yield
  • core: Fix usage of sync.Pool to save an alloc
  • core: Fix data race with sync.RWMutex for uniq
  • core: Prevent QUIC reload panic by lazily initializing the listener
  • core: Refactor/use reflect.TypeFor
  • plugin/auto: Limit regex length
  • plugin/cache: Remove superfluous allocations in item.toMsg
  • plugin/cache: Isolate metadata in prefetch goroutine
  • plugin/cache: Correct spelling of MaximumDefaultTTL in cache and dnsutil packages
  • plugin/dnstap: Better error handling (redial & logging) when Dnstap is busy
  • plugin/file: Performance finetuning
  • plugin/forward: Disallow NOERROR in failover
  • plugin/forward: Added support for per-nameserver TLS SNI
  • plugin/forward: Prevent busy loop on connection err
  • plugin/forward: Add max connect attempts knob
  • plugin/geoip: Add ASN schema support
  • plugin/geoip: Add support for subdivisions
  • plugin/kubernetes: Fix kubernetes plugin logging
  • plugin/multisocket: Cap num sockets to prevent OOM
  • plugin/nomad: Support service filtering
  • plugin/rewrite: Pre-compile CNAME rewrite regexp
  • plugin/secondary: Fix reload causing secondary plugin goroutine to leak

• Update to version 1.13.1:

  • core: Avoid string concatenation in loops
  • core: Update golang to 1.25.2 and golang.org/x/net to v0.45.0 on CVE fixes
  • plugin/sign: Reject invalid UTF‑8 dbfile token

• Update to version 1.13.0:

  • core: Export timeout values in dnsserver.Server
  • core: Fix Corefile infinite loop on unclosed braces
  • core: Fix Corefile related import cycle issue
  • core: Normalize panics on invalid origins
  • core: Rely on dns.Server.ShutdownContext to gracefully stop
  • plugin/dnstap: Add bounds for plugin args
  • plugin/file: Fix data race in tree Elem.Name
  • plugin/forward: No failover to next upstream when receiving SERVFAIL or REFUSED response codes
  • plugin/grpc: Enforce DNS message size limits
  • plugin/loop: Prevent panic when ListenHosts is empty
  • plugin/loop: Avoid panic on invalid server block
  • plugin/nomad: Add a Nomad plugin
  • plugin/reload: Prevent SIGTERM/reload deadlock

• fix CVE-2025-58063 bsc#1249389

• Update to version 1.12.4:

  • bump deps
  • fix(transfer): goroutine leak on axfr err (#7516)
  • plugin/etcd: fix import order for ttl test (#7515)
  • fix(grpc): check proxy list length in policies (#7512)
  • fix(https): propagate HTTP request context (#7491)
  • fix(plugin): guard nil lookups across plugins (#7494)
  • lint: add missing prealloc to backend lookup test (#7510)
  • fix(grpc): span leak on error attempt (#7487)
  • test(plugin): improve backend lookup coverage (#7496)
  • lint: enable prealloc (#7493)
  • lint: enable durationcheck (#7492)
  • Add Sophotech to adopters list (#7495)
  • plugin: Use %w to wrap user error (#7489)
  • fix(metrics): add timeouts to metrics HTTP server (#7469)
  • chore(ci): restrict token permissions (#7470)
  • chore(ci): pin workflow dependencies (#7471)
  • fix(forward): use netip package for parsing (#7472)
  • test(plugin): improve test coverage for pprof (#7473)
  • build(deps): bump github.com/go-viper/mapstructure/v2 (#7468)
  • plugin/file: fix label offset problem in ClosestEncloser (#7465)
  • feat(trace): migrate…

This update for log4j fixes the following issues:

Security fixes:

• CVE-2025-68161: Fixed absent TLS hostname verification that may allow a man-in-the-middle attack (bsc#1255427)

Other fixes:

• Upgrade to 2.18.0
  • Added
    • Add support for Jakarta Mail API in the SMTP appender.
    • Add support for custom Log4j 1.x levels.
    • Add support for adding and retrieving appenders in Log4j 1.x bridge.
    • Add support for custom LMAX disruptor WaitStrategy configuration.
    • Add support for Apache Extras' RollingFileAppender in Log4j 1.x bridge.
    • Add MutableThreadContextMapFilter.
    • Add support for 24 colors in highlighting
  • Changed
    • Improves ServiceLoader support on servlet containers.
    • Make the default disruptor WaitStrategy used by Async Loggers garbage-free.
    • Do not throw UnsupportedOperationException when JUL ApiLogger::setLevel is called.
    • Support Spring 2.6.x.
    • Move perf tests to log4j-core-its
    • Upgrade the Flume Appender to Flume 1.10.0
  • Fixed
    • Fix minor typo #792.
    • Improve validation and reporting of configuration errors.
    • Allow enterprise id to be an OID fragment.
    • Fix problem with non-uppercase custom levels.
    • Avoid ClassCastException in JeroMqManager with custom LoggerContextFactory #791.
    • DirectWriteRolloverStrategy should use the current time when creating files.
    • Fixes the syslog appender in Log4j 1.x bridge, when used with a custom layout.
    • log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null.
    • Improve JsonTemplateLayout performance.
    • Fix resolution of non-Log4j properties.
    • Fixes Spring Boot logging system registration in a multi-application environment.
    • JAR file containing Log4j configuration isn’t closed.
    • Properties defined in configuration using a value attribute (as opposed to element) are read correctly.
    • Syslog appender lacks the SocketOptions setting.
    • Log4j 1.2 bridge should not wrap components unnecessarily.
    • Update 3rd party dependencies for 2.18.0.
    • SizeBasedTriggeringPolicy would fail to rename files properly when integer pattern contained a leading zero.
    • Fixes default SslConfiguration, when a custom keystore is used.
    • Fixes appender concurrency problems in Log4j 1.x bridge.
    • Fix and test for race condition in FileUtils.mkdir().
    • LocalizedMessage logs misleading errors on the console.
    • Add missing message parameterization in RegexFilter.
    • Add the missing context stack to JsonLayout template.
    • HttpWatcher did not pass credentials when polling.
    • UrlConnectionFactory.createConnection now accepts an AuthorizationProvider as a parameter.
    • The DirectWriteRolloverStrategy was not detecting the correct index to use during startup.
    • Async Loggers were including the location information by default.
    • ClassArbiter’s newBuilder method referenced the wrong class.
    • Don’t use Paths.get() to avoid circular file systems.
    • Fix parsing error, when XInclude is disabled.
    • Fix LevelRangeFilterBuilder to align with log4j1’s behavior.
    • Fixes problem with wrong ANSI escape code for bright colors
    • Log4j 1.2 bridge should generate Log4j 2.x messages based on the parameter runtime type.
• Update to 2.19.0
  • Added
    • Add implementation of SLF4J2 fluent API.
    • Add support for SLF4J2 stack-valued MDC.
  • Changed
    • Add getExplicitLevel method to LoggerConfig.
    • Allow PropertySources to be added.
    • Allow Plugins to be injected with the LoggerContext reference.
  • Fixed
    • Add correct manifest entries for OSGi to log4j-jcl
    • Improve support for passwordless keystores.
    • SystemPropertyArbiter was assigning the value as the name.
    • Make JsonTemplateLayout stack trace truncation operate for each label block.
    • Fix…