---
id: "CVE-2025-49602"
kind: "vulnerability"
aliases: ["CVE-2025-49602"]
title: "Keyfactor EJBCA: removed administrators keep access via cached sessions"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["certificate-authority", "ejbca", "infrastructure", "keyfactor", "self-hosted"]
not_affected_if: ["no-admin-role-changes", "not-ejbca-9"]
published_at: "2026-10-30T17:17:11+00:00"
first_seen_at: "2026-10-30T17:31:38+00:00"
updated_at: "2026-10-30T17:32:23+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49602", "first_seen_at": "2026-10-30T17:31:38+00:00"}]
---

# Keyfactor EJBCA: removed administrators keep access via cached sessions

When an administrator is removed from their role while holding a valid TLS session, EJBCA may cache that authentication longer than its configured maximum, which is about 30 seconds by default. The former administrator keeps access they should no longer have.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Confirm the installed EJBCA version, for example by checking the product's version page or build metadata; the sources do not name the fixed version.
- Review how long authentication caching is configured on the EJBCA instance; the sources do not name the setting.

## Timeline

- 2026-10-30T17:31:38+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-49602

## From the sources

An issue was discovered in Keyfactor EJBCA 9. When an administrator is removed from its administrator role while having a valid TLS session, EJBCA may, in certain circumstances, cache authentication for longer than the configured maximum time (default: 30 seconds), which results in the former administrator retaining access that they should no longer have.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_