# CVE-2025-49602: Keyfactor EJBCA authentication cache persistence after admin removal

Source: https://junglewise.ai/threats/cve-2025-49602-an-issue-was-discovered-in-keyfactor-ejbca-9-when-an  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2025-49602 · Severity: info · Published 2026-10-30

EJBCA is a certificate authority and public key infrastructure management system used by enterprises to issue and manage digital certificates. When an administrator's access is revoked while they maintain an active session, the system may continue to cache their authentication credentials beyond the intended timeout period, allowing the former administrator to retain unauthorized access to sensitive PKI functions.

Vendors: [Keyfactor](https://junglewise.ai/threats/vendors/keyfactor).

## Quick answers

**Is CVE-2025-49602 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-49602 being exploited in the wild.

**How severe is CVE-2025-49602?** Informational severity, published 30 October 2026.

**Which products and versions are affected?** Keyfactor EJBCA 9.

**Is there a fix for CVE-2025-49602?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2025-49602 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-49602?** Check whether you run Keyfactor EJBCA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A caching mechanism in EJBCA 9 fails to invalidate authentication sessions immediately when an administrator is removed from their role. An attacker with a valid TLS session can exploit this race condition to perform administrative actions after losing role privileges, as the authentication cache persists longer than the configured maximum time (default 30 seconds). This affects session-level privilege revocation and requires the attacker to already hold a valid authenticated session at the time of role removal.

## Affected products

- Keyfactor EJBCA 9

## Timeline

- 2026-10-30: disclosed

## References

- [https://keyfactor.com/](https://keyfactor.com/)
- [https://support.keyfactor.com/hc/en-us/articles/38482530573979-Security-advisory-EJBCA-authentication-caching-issue?brand_id=10091330043675](https://support.keyfactor.com/hc/en-us/articles/38482530573979-Security-advisory-EJBCA-authentication-caching-issue?brand_id=10091330043675)

## Related threats

- [Keyfactor EJBCA insufficient authorization in certificate self-renewal](https://junglewise.ai/threats/cve-2025-62819-keyfactor-ejbca-through-9-3-3-performs-insufficient-authorization)