UBUNTU-CVE-2026-34480 (CVE-2026-34480)
Vulnerability from osv_ubuntu – Published: 2026-04-10 16:16 – Updated: 2026-10-17 09:40 – Source websiteApache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-4ubuntu3+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-4ubuntu3+esm2?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-3ubuntu1",
"1.2.17-4ubuntu1",
"1.2.17-4ubuntu2",
"1.2.17-4ubuntu3",
"1.2.17-4ubuntu3+esm1",
"1.2.17-4ubuntu3+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.4-2ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.4-2ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.2-1",
"2.4-1",
"2.4-2",
"2.4-2ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-7ubuntu1+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-7ubuntu1+esm2?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-6ubuntu1",
"1.2.17-7ubuntu1",
"1.2.17-7ubuntu1+esm1",
"1.2.17-7ubuntu1+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-8+deb10u1ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-8+deb10u1ubuntu0.2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-7ubuntu2",
"1.2.17-8",
"1.2.17-8+deb10u1build0.18.04.1",
"1.2.17-8+deb10u1ubuntu0.1",
"1.2.17-8+deb10u1ubuntu0.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.12.4-0ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.12.4-0ubuntu0.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.8.2-1",
"2.8.2-2",
"2.10.0-1",
"2.10.0-2",
"2.10.0-2ubuntu0.1",
"2.12.4-0ubuntu0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-9ubuntu0.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-9ubuntu0.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-8",
"1.2.17-9",
"1.2.17-9ubuntu0.1",
"1.2.17-9ubuntu0.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.17.1-0.20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.17.1-0.20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.11.1-2",
"2.11.2-1",
"2.15.0-0.20.04.1",
"2.16.0-0.20.04.1",
"2.17.0-0.20.04.1",
"2.17.1-0.20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-11"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-11?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-10",
"1.2.17-11"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.17.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.17.1-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.13.3-1",
"2.15.0-1",
"2.16.0-1",
"2.17.0-1",
"2.17.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-11"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-11?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-11"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.19.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.19.0-2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.19.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-11"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-11?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-11"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.19.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.19.0-2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.19.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-11build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-11build1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-11build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.19.0-2build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.19.0-2build1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.19.0-2build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j1.2-java",
"binary_version": "1.2.17-11build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "apache-log4j1.2",
"purl": "pkg:deb/ubuntu/apache-log4j1.2@1.2.17-11build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.17-11",
"1.2.17-11build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblog4j2-java",
"binary_version": "2.19.0-2build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "apache-log4j2",
"purl": "pkg:deb/ubuntu/apache-log4j2@2.19.0-2build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.19.0-2",
"2.19.0-2build1"
]
}
],
"aliases": [],
"details": "Apache Log4j Core\u0027s XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j\u0027s internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.",
"id": "UBUNTU-CVE-2026-34480",
"modified": "2026-10-17T09:40:52Z",
"published": "2026-04-10T16:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-34480"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34480"
},
{
"type": "REPORT",
"url": "https://lists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhb"
},
{
"type": "REPORT",
"url": "https://logging.apache.org/security.html#CVE-2026-34480"
},
{
"type": "REPORT",
"url": "https://github.com/apache/logging-log4j2/pull/4077"
},
{
"type": "REPORT",
"url": "https://logging.apache.org/cyclonedx/vdr.xml"
},
{
"type": "REPORT",
"url": "https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout"
},
{
"type": "REPORT",
"url": "http://www.openwall.com/lists/oss-security/2026/04/10/9"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N",
"type": "CVSS_V4"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-34480"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.