Imprivata Enterprise Access Management up to 26.2.6 inadequate encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.25 |
Summary
A vulnerability classified as problematic has been found in Imprivata Enterprise Access Management up to 26.2.6. The affected element is an unknown function. Performing a manipulation results in inadequate encryption. This vulnerability is reported as CVE-2026-82356. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Imprivata Enterprise Access Management up to 26.2.6. This affects some unknown processing. The manipulation with an unknown input leads to a inadequate encryption vulnerability. CWE is classifying the issue as CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. This is going to have an impact on confidentiality. The summary by CVE is:
Imprivata EAM <=26.2.6 lacks the ability to rotate its RSA key pair after deployment when generating an X.509 certificate. Using an RSA key pair indefinitely for certificate generation is against best practices.
It is possible to read the advisory at kb.cert.org. This vulnerability is uniquely identified as CVE-2026-82356 since 08/28/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Inadequate encryptionCWE: CWE-326 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/28/2026 CVE reserved09/23/2026 Advisory disclosed
09/23/2026 VulDB entry created
09/23/2026 VulDB entry last update
Sources
Advisory: kb.cert.orgStatus: Not defined
CVE: CVE-2026-82356 (🔒)
GCVE (CVE): GCVE-0-2026-82356
GCVE (VulDB): GCVE-100-409107
Entry
Created: 09/23/2026 20:59Changes: 09/23/2026 20:59 (52)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.