Is CVE-2025-62819 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-62819 being exploited in the wild.

How severe is CVE-2025-62819?

Informational severity, published 2 November 2026.

Is there a fix for CVE-2025-62819?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-62819 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-62819?

Check whether you run Keyfactor EJBCA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-62819: Keyfactor EJBCA insufficient authorization in certificate self-renewal

CVE-2025-62819 · Severity: info · Published 2026-11-02

Keyfactor EJBCA is a public key infrastructure (PKI) system that manages digital certificates for securing communications and authentication. A flaw in the RA (Registration Authority) web interface allows an authenticated user to renew their own client certificate even when their account status or certificate policies should prohibit this. An attacker with a valid client certificate and RA access could maintain persistent authentication beyond their intended certificate lifetime.

Vendors: Keyfactor.

Quick answers

Is CVE-2025-62819 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-62819 being exploited in the wild.
How severe is CVE-2025-62819?: Informational severity, published 2 November 2026.
Which products and versions are affected?: Keyfactor EJBCA through 9.3.3.
Is there a fix for CVE-2025-62819?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-62819 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-62819?: Check whether you run Keyfactor EJBCA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authorization bypass in EJBCA's certificate self-renewal functionality within the RA web interface. An authenticated user with a valid TLS client certificate and RA access can bypass end-entity status checks and certificate profile renewal restrictions to renew their certificate when they should not be permitted to do so. The attacker must already be authenticated and authorized to access the RA interface, either directly with a certificate or via PublicAccessAuthenticationToken role membership.

Affected products

Keyfactor EJBCA through 9.3.3

Timeline

2026-11-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.