Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,384
Published in 7 days
1,885
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “Apache Log4j”

22 vulnerabilities
  1. Medium 6.3

    CVE-2026-49844 · Apache Log4j

    Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0. The fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity),…

    Published 10 Jul 2026 · Fixed in 2.25.5 · NVD
  2. Medium 6.3

    CVE-2026-34481 · Apache Log4j

    Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An…

    Published 10 Apr 2026 · Fixed in 2.25.4 · NVD
  3. Medium 6.9

    CVE-2026-34480 · Apache Log4j

    Apache 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…

    Published 10 Apr 2026 · Fixed in 2.25.4 · NVD
  4. Medium 6.9

    CVE-2026-34479 · Apache Log4j

    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…

    Published 10 Apr 2026 · Fixed in 2.25.4 · NVD
  5. Medium 6.9

    CVE-2026-34478 · Apache Log4j

    Apache Log4j Core's Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes. Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly: * The newLineEscape…

    Published 10 Apr 2026 · Fixed in 2.25.4 · NVD
  6. Medium 6.3

    CVE-2026-34477 · Apache Log4j

    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…

    Published 10 Apr 2026 · Fixed in 2.25.4 · NVD
  7. Medium 6.3

    CVE-2025-68161 · Apache Log4j

    The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName…

    Published 18 Dec 2025 · Fixed in 2.25.3 · NVD
  8. High 8.8

    CVE-2023-50780 · Apache ActiveMQ Artemis

    Apache ActiveMQ Artemis allows access to diagnostic information and controls through MBeans, which are also exposed through the authenticated Jolokia endpoint. Before version 2.29.0, this also included the Log4J2 MBean. This MBean is not meant for exposure to non-administrative users. This could eventually allow an authenticated attacker to write arbitrary files to the filesystem and indirectly…

    Published 14 Oct 2024 · Fixed in 2.29.0 · NVD
  9. High 7.5

    CVE-2023-26464 · Apache Log4j

    ** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service…

    Published 10 Mar 2023 · Fixed in 2.0 · NVD
  10. High 8.8

    CVE-2022-23307 · Apache Log4j, Oracle WebLogic Server

    CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.

    Published 18 Jan 2022 · Fixed in 2.0 · NVD
  11. Critical 9.8

    CVE-2022-23305 · Apache Log4j, Oracle WebLogic Server

    By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be…

    Published 18 Jan 2022 · NVD
  12. High 8.8

    CVE-2022-23302 · Apache Log4j, Oracle WebLogic Server

    JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar…

    Published 18 Jan 2022 · NVD
  13. Medium 6.6

    CVE-2021-44832 · Apache Log4j, Oracle WebLogic Server

    Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4,…

    Published 28 Dec 2021 · Fixed in 2.3.2, 2.12.4, 2.17.1 · NVD
  14. Medium 5.9

    CVE-2021-45105 · Apache Log4j, Oracle WebLogic Server

    Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

    Published 18 Dec 2021 · Fixed in 2.3.1, 2.12.3 · NVD
  15. Critical 9.0Actively exploited

    CVE-2021-45046 · Apache Log4j

    It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft…

    Published 14 Dec 2021 · Fixed in 2.12.2, 2.16.0 · NVD
  16. High 7.5

    CVE-2021-4104 · Apache Log4j, Oracle WebLogic Server

    JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2…

    Published 14 Dec 2021 · NVD
  17. Critical 10.0Actively exploited

    CVE-2021-44228 · Apache Log4j

    Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is…

    Published 10 Dec 2021 · Fixed in 2.3.1, 2.12.2, 2.15.0 · NVD
  18. Critical 9.8

    CVE-2020-9493 · Apache Log4j

    A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.

    Published 16 Jun 2021 · Fixed in 2.0 · NVD
  19. Low 3.7

    CVE-2020-9488 · Apache Log4j, Oracle WebLogic Server

    Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1

    Published 27 Apr 2020 · Fixed in 2.3.2, 2.12.3, 2.13.2 · NVD
  20. Critical 9.8

    CVE-2019-17571 · Apache Log4j, Oracle WebLogic Server

    Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

    Published 20 Dec 2019 · NVD
  21. Critical 9.8

    CVE-2019-17531 · Oracle WebLogic Server

    A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a…

    Published 12 Oct 2019 · NVD
  22. Critical 9.8

    CVE-2017-5645 · Apache Log4j, Oracle WebLogic Server

    In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.

    Published 17 Apr 2017 · Fixed in 2.8.2 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.