CVE-2026-49844 (Log4j)
Apache Log4j API MapMessage JSON Encoding Vulnerability
Last Updated: 19th November 2026
| Severity | Medium (CVSS 4.0: 6.3) |
| Status | Not exploitable in EzSign |
| Affected products | None. EzSign versions before 4.6.0 include the affected library but do not use the vulnerable code |
Summary
CVE-2026-49844 is an output encoding flaw in the Apache Log4j API
When a Log4j MapMessage containing a non-finite floating point value (NaN, Infinity or -Infinity) is formatted as JSON, the value is written out as-is, producing output that is not valid JSON. Where an attacker can control such a value, this could be used to corrupt JSON logs or interfere with systems that consume them. This is an incomplete fix for the earlier CVE-2026-34481
The issue can only occur when both of the following are true:
- The application uses
JsonTemplateLayout(or another layout that formatsMapMessageobjects as JSON) - The application logs a
MapMessagethat contains an attacker controlled floating point value
The following versions of the Log4j API are affected:
- 2.13.1 to 2.25.4
- 2.26.0
Am I Vulnerable
No. Versions of EzSign before 4.6.0 include an affected version of the Log4j API, but the vulnerability cannot be exploited
EzSign logs only plain text messages, using a pattern layout (configured in [EzSign Install]\EzSignServer\logconf\log4j2.xml). It does not use JsonTemplateLayout and never creates MapMessage objects, so the vulnerable code is never called
EzSign 4.6.0 includes Log4j version 2.26.1, which is not affected
What Should We Do
No action is required
If you have changed the EzSign logging configuration to use a JSON layout, contact Krestfield Support
If you would like to remove the affected library completely (e.g. so it is no longer reported by vulnerability scanners), upgrade to EzSign 4.6.0
When upgrading, replace the whole EzSignServer/lib folder with the new one, rather than copying the new jars into the existing folder. See Upgrading to EzSign 4.6 for more details
References
Revision History
| Date | Change |
|---|---|
| 19th November 2026 | Initial advisory |
More Information
Contact Krestfield Support for more information