VulnerabilityPublished 30 Oct 2026

CVE-2025-49602: Keyfactor EJBCA

Source GCVE Database

Compare

Authoritative record:CVE-2025-49602· High

Not known to be exploited.

Data as of 30 Oct 2026, 20:19 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9rjg-qmjp-26f2

What to do

AI-suggested

Users should monitor vendor advisories for updates addressing this caching issue. Until a fix is available, administrators should consider terminating active sessions immediately upon role removal to prevent extended access.

Description

A vulnerability in Keyfactor EJBCA 9 allows a removed administrator to retain access longer than intended due to cached authentication sessions. Specifically, when an administrator is removed from their role while having an active TLS session, the system may cache their authentication beyond the configured maximum time (default 30 seconds), potentially allowing unauthorized continued access.

Impact

The impact is unauthorized access persistence by a former administrator who should no longer have administrative privileges. This could allow continued administrative actions during the extended cached authentication period, potentially leading to unauthorized system changes or data access. No evidence of active exploitation or public exploit code is reported.

Summary

CVE-2025-49602 describes a flaw in Keyfactor EJBCA 9 where, if an administrator is removed from their administrator role during an active TLS session, the software may cache the administrator's authentication credentials longer than the configured maximum time. This caching behavior can result in the former administrator retaining access privileges that should have been revoked, thus violating access control policies.

References

Community reviews

Loading reviews…