Lucene search
+L
ApacheLog4j

6 matches found

CVE
CVE
added 2021/12/14 12:00 a.m.1512 views

CVE-2021-4104

CVE-2021-4104 affects JMSAppender in Log4j 1.2 when it is explicitly configured to use JMSAppender. A deserialization of untrusted data can occur if an attacker can write Log4j configuration and supply TopicBindingName and TopicConnectionFactoryBindingName, causing JMSAppender to perform JNDI req...

7.5CVSS9.4AI score0.81147EPSS
SaveIn wildWeb
CVE
CVE
added 2026/04/10 3:42 p.m.1059 views

CVE-2026-34480

Technical details about CVE-2026-34480 are not publicly available in the provided connected documents. The initial description gives an overview but no vendor/product/version specifics or remediation steps here. Monitor for updates from official advisories.

7.5CVSS5.8AI score0.00972EPSS
Save
CVE
CVE
added 2023/03/10 1:38 p.m.320 views

CVE-2023-26464

The CVE-2023-26464 issue affects Apache Log4j 1.x Chainsaw and SocketAppender when running on JRE

7.5CVSS8.2AI score0.01905EPSS
SaveIn wild
CVE
CVE
added 2026/04/10 3:40 p.m.301 views

CVE-2026-34478

CVE-2026-34478 (Log4j Core) affects Apache Log4j Core 2.21.0 through 2.25.3 and involves CRLF log-injection risks in stream-based syslog output due to undocumented renames of configuration attributes in Rfc5424Layout. Specifically, the newLineEscape attribute was silently renamed, breaking newlin...

7.5CVSS5.8AI score0.00972EPSS
Save
CVE
CVE
added 2026/04/10 3:43 p.m.221 views

CVE-2026-34481

CVE-2026-34481 affects Apache Log4j’s JsonTemplateLayout. Versions up to 2.25.3 produce invalid JSON when log events contain non-finite floating-point values (NaN, Infinity, -Infinity), violating RFC 8259 and potentially causing downstream log processors to reject or fail indexing. Exploitation r...

7.5CVSS6.1AI score0.00691EPSS
Save
CVE
CVE
added 2026/04/10 3:41 p.m.174 views

CVE-2026-34479

The CVE affects the Apache Log4j 1-to-Log4j 2 bridge: Log4j1XmlLayout used in Log4j Core 2 configurations or via the Log4j 1 compatibility layer with org.apache.log4j.xml.XMLLayout. The root cause is failure to properly escape characters forbidden by XML 1.0, producing malformed XML that conformi...

7.5CVSS5.8AI score0.00535EPSS
Save