---
id: CVE-2025-62819
title: >-
  Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when
  self-renewing a client certificate via the RA (Registration Authority) User
  Interface
summary: >-
  Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when
  self-renewing a client certificate via the RA (Registration Authority) User
  Interface. This allows a remote user, authenticated with a valid client
  certificate…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'
cvssSource: adp
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-06T19:15:49.175626Z'
published: '2026-11-02'
updated: '2026-11-06'
sourceUpdated: '2026-11-06T19:15:53.709Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-62819'
references:
  - url: 'https://trust.keyfactor.com'
  - url: >-
      https://support.keyfactor.com/hc/en-us/articles/57971026069531-Security-advisory-EJBCA-unauthorized-client-certificate-renewal-in-RA-Web
tags:
  - cve.org
epss: 0.00213
epssPercentile: 0.11629
ingestedAt: '2026-11-05T19:30:42.666Z'
---

## Overview

Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA (Registration Authority) User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status and/or profile settings should deny renewal. The attacker must have a valid TLS client certificate, and must be authorized to use the RA User Interface, either with the certificate, or via a role membership for PublicAccessAuthenticationToken.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.