An issue was discovered in PrimeKey EJBCA before 7.6.0.

published 2021-08-25 5y ago modified 2026-09-08 2mo ago also BIT-ejbca-2021-40089 , EUVD-2021-27278

cvss: 2.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits: 0; none known

An issue was discovered in PrimeKey EJBCA before 7.6.0. The General Purpose Custom Publisher, which is normally run to invoke a local script upon a publishing operation, was still able to run if the System Configuration setting Enable External Script Access was disabled. With this setting disabled it's not possible to create new such publishers, but existing publishers would continue to run.

Patch / fix

fixed in 2

bitnami ejbca 7.6.0
primekey ejbca 7.6.0

Is CVE-2021-40089 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	2.3	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	1.9	AV:L/AC:M/Au:N/C:N/I:P/A:N
OSV	3.1	2.3	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	ejbca	<7.6.0	7.6.0

References

support.primekey.com /news/posts/54
vendor-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2021-40089
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.