Skip to main content
CVE-2025-62819VulnerabilityPublished

Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-62819· High

Not known to be exploited.

Data as of 2 Nov 2026, 16:58 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

AI-suggested

Until a fix is available, restrict RA User Interface access to trusted users only and monitor certificate renewal activities closely.

Description

Keyfactor EJBCA versions through 9.3.3 have a vulnerability where insufficient authorization checks occur during client certificate self-renewal via the RA User Interface. An authenticated remote user with a valid client certificate and RA UI access can renew their certificate even if policy or profile settings should prevent it.

References

Community reviews

Loading reviews…