Homepage

org.apache.logging.log4j:log4j-api@3.0.0-beta2

  • latest version

    2.26.1

  • latest non vulnerable version

    2.26.1

  • first published

    14 years ago

  • latest version published

    1 months ago

  • licenses detected

  • package registry

    View on Maven Central Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.apache.logging.log4j:log4j-api package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Encoding or Escaping of Output

    Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the MapMessage.asJson() method, which emits the bare NaN, Infinity, or -Infinity tokens instead of an RFC 8259-compliant representation. An attacker can emit malformed JSON that corrupts the enclosing log record or disrupts downstream log ingestion and parsing by supplying non-finite floating-point values that the application records in a logged MapMessage. Exploitation requires the application to use the message resolver of JsonTemplateLayout, or another layout relying on MapMessage.asJson(), and to log a MapMessage holding attacker-controlled floating-point values.

    Note: This is a bypass of the fix for the vulnerability described in CVE-2026-34481.

    How to fix Improper Encoding or Escaping of Output?

    A fix was pushed into the master branch but not yet published.

    [2.13.1,2.25.5)[2.26.0,2.26.1)[3.0.0-alpha1,)
    Go back to all versions of this package