Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration
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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.logging.log4j:log4j-core | >= 2.12.0, < 2.25.4, >= 3.0.0-alpha1, <= 3.0.0-beta3 | 2.25.4 |
Referencias
- https://nvd.nist.gov/vuln/detail/CVE-2026-34477
- https://github.com/apache/logging-log4j2/pull/4075
- https://github.com/apache/logging-log4j2
- https://lists.apache.org/thread/lkx8cl46t2bvkcwfcb2pd43ygc097lq4
- https://logging.apache.org/cyclonedx/vdr.xml
- https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName
- https://logging.apache.org/security.html#CVE-2026-34477
- Vector CVSS
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N- Debilidad (CWE)
CWE-297- Plataforma
- Java / Kotlin (Maven)
- Paquete
org.apache.logging.log4j:log4j-core- Publicada
- 10.04.2026
- Actualizado
- 11.10.2026 13:20
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-6hg6-v5c8-fphq - CC BY 4.0
Historial de vulnerabilidades: org.apache.logging.log4j:log4j-core
Todas las vulnerabilidades publicadas de este paquete (Java / Kotlin (Maven)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 11
- Primera → última
- 01.2020 04.2026
- Sin corrección
- 0
- Explotada en ataques
- 2
Distribución por gravedad
- Crítica 3
- Alta 2
- Media 5
- Baja 1
Divulgaciones por año
- 2020: 2
- 2021: 3
- 2022: 1
- 2023: 1
- 2024: 0
- 2025: 1
- 2026: 3
-
Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.