Security Advisories
This section lists publicly disclosed vulnerabilities that may affect Krestfield products, together with the steps you should take
Each advisory states which products and versions are affected, which are not affected, and what to do. Advisories are updated as new information becomes available. Check the revision history at the bottom of each page
Current Advisories
| Advisory | Products | Severity | Status | Last Updated |
|---|---|---|---|---|
| CVE-2026-114938 (Java4Shell) | EzSign, Certdog | Critical | Action required | 19th November 2026 |
| CVE-2026-89425 (Jackson) | EzSign (before 4.6.0, Azure Key Vault only) | High | Fixed in EzSign 4.6.0 | 19th November 2026 |
| CVE-2026-58062 (Bouncy Castle) | EzSign (before 4.6.0) | Critical | Not exploitable | 19th November 2026 |
| CVE-2026-49844 (Log4j) | EzSign (before 4.6.0) | Medium | Not exploitable | 19th November 2026 |
Subscribe
To be notified of new and updated advisories, subscribe to the RSS feed
More Information
To report a vulnerability or for more information, contact Krestfield Support
Table of contents
- CVE-2026-114938 (Java4Shell) - Critical OpenJDK Base64 decoder flaw (Java4Shell). EzSign customers should replace their Java runtime with a patched build. Certdog customers should run the Java upgrade script.
- CVE-2026-89425 (Jackson) - Denial of service flaw in FasterXML jackson-core. EzSign versions before 4.6.0 include the affected library but are only affected when Azure Key Vault is used as a key store. Fixed in EzSign 4.6.0.
- CVE-2026-58062 (Bouncy Castle) - Bouncy Castle stapled OCSP response flaw. Not exploitable in EzSign, which performs its own OCSP validation. EzSign 4.6.0 does not include the affected library.
- CVE-2026-49844 (Log4j) - Apache Log4j API MapMessage JSON encoding flaw. Not exploitable in EzSign, which only logs plain text messages. EzSign 4.6.0 does not include the affected library.