cve.bz

CVE-2026-34477 apache log4j: Improper Certificate Validation

6.3 mediumEPSS 0.6%Fix available

Medium (6.3) in apache log4j. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.logging.log4j:log4j-core 2.25.4.

On this page
The fix for CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-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 https://logging.apache.org/log4j/2.x/manual/appenders/network.html#HttpAppender-attr-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.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-295 Improper Certificate Validation
CWE-297 Improper Validation of Certificate with Host Mismatch
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34477 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34477?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34477?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34477 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-34477

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-34477](https://cve.bz/cve/badge/CVE-2026-34477.svg)](https://cve.bz/cve/CVE-2026-34477)

HTML:

<a href="https://cve.bz/cve/CVE-2026-34477"><img src="https://cve.bz/cve/badge/CVE-2026-34477.svg" alt="CVE-2026-34477"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Log4j Corefrom 2.12.0 before 2.25.4
Apache Software Foundation Apache Log4j Corefrom 3.0.0-alpha1 through 3.0.0-beta3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6hg6-v5c8-fphqMavenorg.apache.logging.log4j:log4j-core>=2.12.0 <2.25.42.25.4
GHSA-6hg6-v5c8-fphqMavenorg.apache.logging.log4j:log4j-core>=3.0.0-alpha1 <=3.0.0-beta3no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 5 moreapache-log4j2no fix listedUBUNTU-CVE-2026-34477
openSUSETumbleweedlog4j2.20.0-2.1openSUSE-SU-2026:10544-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Offline Knowledge Portal 1.2.13offline-knowledge-portal/rhokp-rhel9:1779996999Fixed 2026-05-28RHSA-2026:21773
Red Hat AI Inference Serverredhat-user-workloads/rhaiis-cuda-ubi9-3-2-2Fix deferred
Red Hat AI Inference Serverredhat-user-workloads/rhaiis-cuda-ubi9-3-3Fix deferred
Red Hat AMQ Broker 7log4j-coreFix deferred
Red Hat build of Apache Camel for Spring Boot 4log4j-coreFix deferred
Red Hat build of Apache Camel - HawtIO 4log4j-coreFix deferred
Red Hat build of Apicurio Registry 2log4j-coreFix deferred
Red Hat build of Apicurio Registry 3log4j-coreFix deferred
Red Hat build of OptaPlanner 8log4j-coreFix deferred
Red Hat Data Grid 8log4j-coreFix deferred
Red Hat Data Grid 8log4j-core-testFix deferred
Red Hat Enterprise Linux 8log4j:2/log4jFix deferred
Red Hat Enterprise Linux 8pki-core:10.6/resteasyFix deferred
Red Hat Enterprise Linux 8pki-deps:10.6/resteasyFix deferred
Red Hat Enterprise Linux 9log4jOut of support scope
Red Hat Enterprise Linux 9resteasyFix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3bazel7Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3bazel8Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3redhat-user-workloads/bootc-cuda-aws-3-3Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3redhat-user-workloads/bootc-cuda-azure-3-3Fix deferred
27 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-34477.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON