VU#273940: Enterprise Access Management EAM does not rotate RSA keys
Imprivata Enterprise Access Management (EAM) versions 26.2.6 and below do not support rotation of the RSA key pair used to generate the appliance's X.509 certificate. This means the same key pair is used indefinitely, violating cryptographic best practices. If an attacker obtains the private key, they can impersonate the appliance to any trusted endpoint, intercepting authentication traffic and potentially decrypting past communications if perfect forward secrecy is not enforced. The vendor is aware but has not provided a fix or timeline. Until resolved, users should protect the private key and enforce perfect forward secrecy.
AI Analysis
Technical Summary
Imprivata EAM uses a single RSA key pair indefinitely to generate its X.509 certificate for appliance identification to clinical workstations and EHR platforms. There is no supported mechanism to rotate this key pair after deployment. This vulnerability (CVE-2026-82356) allows an attacker who obtains the private key—via backup exfiltration, hypervisor snapshots, or privileged filesystem access—to impersonate the appliance and intercept authentication traffic across all applications relying on it. The inability to rotate or revoke the key without redeploying the appliance prolongs the risk. The vendor has acknowledged the issue internally but has not released a fix or timeline.
Potential Impact
An attacker with access to the private RSA key can impersonate the Imprivata EAM appliance to any endpoint trusting its certificate, enabling persistent and stealthy interception of authentication traffic, including SSO tokens and credentials for clinical systems. Without perfect forward secrecy, previously captured traffic can be decrypted retroactively. This access persists indefinitely until the appliance is redeployed, as there is no supported key rotation or revocation mechanism.
Mitigation Recommendations
No official fix or timeline is currently available. Until a resolution is provided, users should protect the appliance's private RSA key by restricting filesystem and administrative access, securing backups and hypervisor snapshots, and enforcing perfect forward secrecy on upstream connections to limit the impact of any key compromise.
VU#273940: Enterprise Access Management EAM does not rotate RSA keys
Description
Imprivata Enterprise Access Management (EAM) versions 26.2.6 and below do not support rotation of the RSA key pair used to generate the appliance's X.509 certificate. This means the same key pair is used indefinitely, violating cryptographic best practices. If an attacker obtains the private key, they can impersonate the appliance to any trusted endpoint, intercepting authentication traffic and potentially decrypting past communications if perfect forward secrecy is not enforced. The vendor is aware but has not provided a fix or timeline. Until resolved, users should protect the private key and enforce perfect forward secrecy.
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Imprivata EAM uses a single RSA key pair indefinitely to generate its X.509 certificate for appliance identification to clinical workstations and EHR platforms. There is no supported mechanism to rotate this key pair after deployment. This vulnerability (CVE-2026-82356) allows an attacker who obtains the private key—via backup exfiltration, hypervisor snapshots, or privileged filesystem access—to impersonate the appliance and intercept authentication traffic across all applications relying on it. The inability to rotate or revoke the key without redeploying the appliance prolongs the risk. The vendor has acknowledged the issue internally but has not released a fix or timeline.
Potential Impact
An attacker with access to the private RSA key can impersonate the Imprivata EAM appliance to any endpoint trusting its certificate, enabling persistent and stealthy interception of authentication traffic, including SSO tokens and credentials for clinical systems. Without perfect forward secrecy, previously captured traffic can be decrypted retroactively. This access persists indefinitely until the appliance is redeployed, as there is no supported key rotation or revocation mechanism.
Mitigation Recommendations
No official fix or timeline is currently available. Until a resolution is provided, users should protect the appliance's private RSA key by restricting filesystem and administrative access, securing backups and hypervisor snapshots, and enforcing perfect forward secrecy on upstream connections to limit the impact of any key compromise.
Technical Details
- Classification
- {"confidence":0.71,"severitySource":"default","classifier":"rss-v2"}
- Article Source
- {"url":"https://kb.cert.org/vuls/id/273940","fetched":true,"fetchedAt":"2026-09-23T18:30:10.259Z","wordCount":563}
Threat ID: 6ab41ab2f7a7c5410629a2e3
Added to database: 09/23/2026, 18:30:10 UTC
Last enriched: 09/23/2026, 18:30:25 UTC
Last updated: 09/24/2026, 03:05:00 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.