Security readout for executives and security teams
Plain-English summary
PrimeKey EJBCA before 7.6.0 could expose enrollment secrets for SCEP, CMP, EST, and Auto-enrollment aliases in administrator-viewable page source. The secret was hidden from normal view but recoverable by inspecting the page HTML.
Executive priority
Treat as a focused certificate-management exposure. It is not documented as internet-exploited, but leaked enrollment secrets can weaken trust workflows if administrator accounts or page source records were exposed.
Technical view
The issue is an information disclosure in EJBCA alias configuration pages. Enrollment secrets for SCEP, CMP, EST, and Auto-enrollment were reflected into page source accessible to administrators, creating risk if admin access was shared, delegated, monitored, or compromised.
Likely exposure
Organizations running PrimeKey EJBCA versions before 7.6.0 and using SCEP, CMP, EST, or Auto-enrollment aliases may be exposed. Evidence does not identify broader affected products or exact configurations beyond those aliases.
Exploitation context
The source bundle does not show active exploitation, KEV listing, public exploit details, CVSS, or CWE classification. Access appears limited to administrators who can view the relevant configuration page source.
Researcher notes
Available evidence is sparse: no CVSS, CWE, exploit telemetry, or detailed vendor remediation text is included. The key validation question is whether affected aliases existed before upgrading from an EJBCA version earlier than 7.6.0.
Mitigation direction
- Confirm whether EJBCA is before version 7.6.0.
- Review PrimeKey guidance for fixed-version and operational instructions.
- Upgrade EJBCA to 7.6.0 or later if affected.
- Rotate enrollment secrets that may have appeared in page source.
- Review administrator access and audit logs around affected pages.
Validation and detection
- Inventory EJBCA versions across CA management environments.
- Identify configured SCEP, CMP, EST, and Auto-enrollment aliases.
- Confirm affected alias pages no longer expose secrets in source.
- Check whether any exposed secrets remain active.
- Review admin access records during the exposure window.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-40086 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://support.primekey.com/news/posts/52CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.