Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-34479: The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML

52
This week
HIGH 7.5REMOTEWATCHLISTUPGRADE

CVE-2026-34479 is a high-severity flaw (CVSS 7.5) affecting log4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records. Two groups of users are affected: * Those using Log4j1XmlLayout directly in a Log4j Core 2 co

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 55%)
CISA exploited listNo
WeaknessCWE-116
Published2026-04-10
Last modified2026-10-26
Publisher (CNA): Apache Software Foundation · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache log4j UPGRADE
Affected: >= 2.7 and < 2.25.4 · 3.0.0 alpha1 · 3.0.0 alpha1_rc1 · 3.0.0 alpha1_rc2 · 3.0.0 beta1 · 3.0.0 beta2
Fixed in: 2.25.4
Safe to downgrade to: a release before 2.7
1. Check installed version
apt-cache policy log4j || rpm -q log4j || log4j --version
2. UPGRADE to 2.25.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade log4j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade log4j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.7 (Debian / Ubuntu)
apt-cache madison log4j sudo apt install log4j=<VERSION_BEFORE_2.7> sudo apt-mark hold log4j
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list log4j sudo dnf downgrade log4j-<VERSION_BEFORE_2.7> sudo dnf versionlock add log4j
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-34479?

log4j: upgrade to 2.25.4. Exact commands for each OS are on this page.

Is CVE-2026-34479 being exploited?

CVE-2026-34479 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-34479 affect?

CVE-2026-34479 affects log4j. Severity is high (CVSS 7.5). The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters w

How urgent is CVE-2026-34479?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Apache Log4j vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.