Credential disclosure via shared configuration encryption key
Published Oct 2, 2026 · Updated Oct 2, 2026
Hard-coded key reuse in Armatura LLC Armatura One before 4.7.2 and Armatura One (USA) before 4.6.1 allows attackers to decrypt stored credentials. The installation configuration encrypts database and message-broker credentials with AES-128-CBC using a key and initialization vector fixed across installations. Exploitation requires a copy of the installation package to recover those values and separate access to the target installation's encrypted configuration file.
Summary
What happened
Hard-coded key reuse in Armatura LLC Armatura One before 4.7.2 and Armatura One (USA) before 4.6.1 allows attackers to decrypt stored credentials. The installation configuration encrypts database and message-broker credentials with AES-128-CBC using a key and initialization vector fixed across installations. Exploitation requires a copy of the installation package to recover those values and separate access to the target installation's encrypted configuration file.
The record
- CVE
- CVE-2026-94591
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- Armatura LLC
- Product
- Armatura One
- Classifications
- CWE-321, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.7.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started