Keyfactor EJBCA up to 9.3.3 RA User Interface improper authorization

Summaryinfo

A vulnerability was found in Keyfactor EJBCA up to 9.3.3. It has been declared as problematic. The impacted element is an unknown function of the component RA User Interface. The manipulation results in improper authorization. This vulnerability is identified as CVE-2025-62819. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Keyfactor EJBCA up to 9.3.3. Affected is some unknown processing of the component RA User Interface. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at trust.keyfactor.com. This vulnerability is traded as CVE-2025-62819 since 10/23/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation needs additional levels of successful authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/02/2026). The MITRE ATT&CK project declares the attack technique as T1548.002.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Keyfactor

Name

• EJBCA

Version

• 9.3.0
• 9.3.1
• 9.3.2
• 9.3.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion