{"id":"CVE-2025-62819","kind":"vulnerability","aliases":["CVE-2025-62819"],"related":[],"title":"Keyfactor EJBCA: client certificate self-renewal skips authorization checks","description":"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.","summary":"Keyfactor EJBCA through 9.3.3 fails to enforce end entity status and profile rules when a user renews their own client certificate through the RA web interface. An attacker who already holds a valid client certificate can renew it even where renewal should be denied.","severity":"medium","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["ejbca","infrastructure","keyfactor","pki","self-hosted"],"not_affected_if":["no-public-access-role","ra-ui-not-exposed"],"how_to_check":"- Check the installed EJBCA version against the affected range (through `9.3.3`).\n- Confirm whether the RA User Interface is exposed and who holds roles for `PublicAccessAuthenticationToken`.","fix":null,"status":"open","published_at":"2026-11-02T15:17:11+00:00","first_seen_at":"2026-11-02T15:24:01+00:00","triaged_at":"2026-11-02T15:26:34+00:00","updated_at":"2026-11-02T15:26:34+00:00","category":"infrastructure","confidence":0.6,"triage":{"at":"2026-11-02T15:26:34Z","model":"claude-haiku-5-5","output":{"fix":"- unknown","reach":"network","title":"Keyfactor EJBCA: client certificate self-renewal skips authorization checks","impact":"medium","summary":"Keyfactor EJBCA through 9.3.3 fails to enforce end entity status and profile rules when a user renews their own client certificate through the RA web interface. An attacker who already holds a valid client certificate can renew it even where renewal should be denied.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["ejbca","keyfactor","pki","self-hosted"],"confidence":0.6,"fix_status":"unknown","needs_auth":"yes","worst_case":"authenticated user renews certificate despite denial rules","analyst_note":"Sources give no fixed version or vendor advisory; check the Keyfactor EJBCA security advisory for a fixed release and the RA UI setting.","how_to_check":"- Check the installed EJBCA version against the affected range (through `9.3.3`).\n- Confirm whether the RA User Interface is exposed and who holds roles for `PublicAccessAuthenticationToken`.\n- unknown","plain_action":"","needs_analyst":true,"not_affected_if":["ra-ui-not-exposed","no-public-access-role"],"who_is_affected":"Organizations running Keyfactor EJBCA 9.3.3 or earlier with the RA User Interface reachable by users who already hold client certificates. Per the description, the attacker needs a valid client certificate and RA UI authorization, either via the certificate or a role membership for PublicAccessAuthenticationToken. Deployments without the RA UI exposed or without such role membership are less exposed; the sources do not say more.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000729,"input_tokens":4192,"output_tokens":619,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-2025':12A,15A '-62819':13A,16A '9.3.3':27B,71C 'allow':91C 'alreadi':53B 'and/or':111C 'attack':51B,118C 'authent':95C 'author':9A,74C,87C,129C 'certif':4A,44B,58B,82C,100C,104C,125C,139C 'check':10A,75C 'client':3A,43B,57B,81C,99C,124C 'cve':11A,14A 'deni':67B,115C 'either':136C 'ejbca':2A,17B,25B,69C 'end':31B,108C 'enforc':30B 'entiti':32B,109C 'even':62B,105C 'fail':28B 'hold':54B 'host':23B 'infrastructur':18B 'insuffici':73C 'interfac':49B,89C,135C 'keyfactor':1A,19B,24B,68C 'membership':144C 'must':119C,127C 'perform':72C 'pki':20B 'profil':35B,112C 'publicaccessauthenticationtoken':146C 'ra':47B,85C,133C 'registr':86C 'remot':93C 'renew':7A,40B,60B,64B,79C,102C,116C 'role':143C 'rule':36B 'self':6A,22B,78C 'self-host':21B 'self-renew':5A,77C 'set':113C 'skip':8A 'status':33B,110C 'tls':123C 'use':131C 'user':39B,88C,94C,134C 'valid':56B,98C,122C 'via':83C,141C 'web':48B","nicknames":[],"mitigations":[],"who_affected":"Organizations running Keyfactor EJBCA 9.3.3 or earlier with the RA User Interface reachable by users who already hold client certificates. Per the description, the attacker needs a valid client certificate and RA UI authorization, either via the certificate or a role membership for PublicAccessAuthenticationToken. Deployments without the RA UI exposed or without such role membership are less exposed; the sources do not say more.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"none","audience":"businesses","plain_action":null,"pkeys":[],"ptokens":[],"labels":["ejbca","infrastructure","keyfactor","medium","pki","selfhosted"],"first_public_at":"2026-11-02T15:17:11+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2025-62819","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-62819","severity":null,"published_at":"2026-11-02T15:17:11+00:00","modified_at":"2026-11-02T15:17:11+00:00","first_seen_at":"2026-11-02T15:24:01+00:00","fetched_at":"2026-11-02T15:24:01+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}