Skip to main content

Armatura One CVE-2026-94591

| EUVDEUVD-2026-91834 HIGH
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-02 icscert GHSA-rpcg-4hqj-wfv3
8.6
CVSS 4.0 · Vendor: icscert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain installation package and target config file
  2. Exploit
    Extract hardcoded AES key and IV from binary
  3. Execution
    Decrypt stored credentials offline
  4. Impact
    Authenticate to database/message broker with recovered credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

Exploitation requires that the optional credential-encryption protection be enabled so credentials are stored AES-128-CBC-encrypted in the install configuration file, and that the attacker (1) possess a copy of the Armatura One installation package to recover the universal embedded key and IV, and (2) separately obtain the specific target installation's encrypted configuration file. The limiting factor is this second prerequisite: the flaw grants no remote network access by itself (AV:L) - the attacker must already have a path to read the victim's config file (local/filesystem access, a stolen backup, or an exposed share) before the hardcoded key yields the plaintext database and message-broker credentials.

Impact

The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N, VC:H/VI:H/VA:H, score 8.6) correctly reflects a local attack vector: although privileges are not required (PR:N), successful exploitation hinges on the attacker first obtaining a copy of a target installation's encrypted configuration file plus the installation package - this is not remotely triggerable, which materially lowers real-world urgency relative to the 8.6 headline. CWE-321 (hard-coded cryptographic key) is confirmed by the description, which states the AES-128-CBC key and IV are fixed, embedded in the software, and identical across every installation. No EPSS score, CISA KEV listing, or public POC was provided in the input; per precision rules this is 'no public exploit identified at time of analysis,' so there is no evidence of active or automatable exploitation. The high confidentiality/integrity/availability impact is plausible because recovered database and message-broker credentials could grant broad backend access, but the impact is conditional on separately exfiltrating the config file - a prerequisite the CVSS vector captures as AV:L rather than AV:N. Net: this is a genuine, well-characterized cryptographic weakness worth remediating, but the local/precondition-dependent exploitation path makes it a targeted rather than mass-exploitation risk, not a drop-everything network-facing threat.

Exploit ScenarioDerived

An attacker downloads the publicly or commercially available Armatura One installation package and statically extracts the embedded, universal AES-128-CBC key and initialization vector. Having separately obtained a specific victim's encrypted install configuration file (e.g., via filesystem access, a backup, or a misconfigured share), the attacker decrypts it offline to recover the plaintext database and message-broker credentials. No public exploit code is identified at time of analysis, but the attack requires only standard reverse-engineering effort (AC:L).

Act Now Prioritize within 24-48h. Why: Active threat signals + CRITICAL/HIGH severity.
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Oct 02, 2026

Armatura One and Armatura One (USA) installations that enable the optional AES-128-CBC credential protection store database and message-broker credentials under a hard-coded key and IV embedded in the software, so an attacker who has the installation package and separately obtains a target's encrypted install configuration file can decrypt those credentials. The independent assessment scores this as 8.6 but emphasizes a local attack vector: it is not remotely triggerable and requires prior access to the victim's configuration file, with no privileges required (PR:N) but a local prerequisite (AV:L). No public exploit identified at time of analysis.

Earlier versions of this analysis (1)
v1 Oct 02, 2026 - 22:17 CVSS 8.4

Armatura One deployments that enable encrypted credential storage can have their stored database and message-broker credentials recovered by anyone who obtains both the Armatura One installation package and the target installation's encrypted install configuration file, because the AES-128-CBC key and initialization vector protecting those credentials are hard-coded and identical across every installation. The flaw is rated CVSS 3.1 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and requires two prerequisites - a copy of the installer and a copy of the victim's config file - so exploitation is local and file-dependent rather than remotely reachable through this issue alone; no public exploit code was identified at time of analysis and there is no CISA KEV listing. Successful recovery of database and broker credentials gives the attacker High impact to confidentiality, integrity and availability of the affected Armatura One environment, as the stolen credentials can be used to read or alter backend data and messaging infrastructure.

RemediationAI

No vendor-released patch is identified in the provided data; consult CISA ICS advisory ICSA-26-274-01 for current vendor guidance and any updated fixed version. Because the key and IV are hard-coded and universal, until a vendor fix replaces them, treat all encrypted credentials in Armatura One configuration files as recoverable by anyone who has both the install package and the config file. Practical mitigations include restricting read access to the install configuration file to the minimum necessary service accounts and administrators, storing it on encrypted volumes, excluding it from support bundles and unprotected backups, and rotating database and message-broker credentials after any suspected configuration exposure. Network-isolating the database and message broker can also reduce the immediate usability of recovered credentials. These controls have trade-offs: tight file permissions can break automated backup or troubleshooting workflows, and credential rotation may disrupt running integrations. If the vendor releases a fix with a new key-management design, it should be prioritized, but no exact fixed version is available in the input.

Affected VersionsENISA

Armatura One 0 <4.7.2
Armatura One (USA) 0 <4.6.1

Affected Packages

euvd armatura_one fix: 4.7.2
euvd armatura_one_usa fix: 4.6.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-321 Use of Hard-coded Cryptographic Key. Armatura One stores database and message-broker credentials in an installation configuration file; when credential encryption is enabled, AES-128-CBC is used. CBC mode requires a unique unpredictable IV per operation, but the product uses a fixed key and IV embedded in the installation package, identical across all deployments. Because the key is universal, possession of any copy of the package yields the key and IV; each target then only requires its own encrypted configuration file, which the attacker must obtain via local filesystem access, a stolen backup, or an exposed share. CPE wildcards for armatura_llc:armatura_one and armatura_llc:armatura_one_(usa) indicate no version restriction in the available data, and CISA ICS advisory ICSA-26-274-01 is the primary reference.

Know when Armatura One gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (icscert) PRIMARY 8.6 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.4 HIGH

AV:L because the attacker must obtain the local config file; AC:L and PR:N since the universal key is trivially extracted with no auth; C/I/A:H as recovered DB and broker credentials enable full backend compromise.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (icscert).

CVSS VectorVendor: icscert

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch available
Oct 02, 2026 - 23:17 EUVD
CVSS changed
Oct 02, 2026 - 22:22 NVD
8.4 (HIGH) 8.6 (HIGH)
CVE Published
Oct 02, 2026 - 21:54 cve.org
HIGH 8.4

DescriptionCVE.org

Armatura One stores database and message-broker credentials in an install configuration file, encrypting them with AES-128-CBC when this protection is enabled. The encryption key and initialization vector are fixed values embedded in the software itself and are identical across every installation. An attacker with a copy of the installation package can recover this key and initialization vector, and can then decrypt the stored credentials of any specific installation to which the attacker separately obtains the encrypted configuration file.

Executive ViewAI

Why It Matters

Armatura One and Armatura One (USA) installations that enable the optional AES-128-CBC credential protection store are affected by a hard-coded key and IV issue, which can allow decryption of database and message-broker credentials if an attacker obtains the encrypted install configuration file and the installation package. Because exploitation requires local access to those files and is not remotely triggerable, the immediate organizational risk is elevated for environments where configuration files or backups are broadly accessible, but there is no public exploit identified at time of analysis. Leadership should prioritize inventorying affected deployments, limiting access to sensitive install artifacts, and rotating any credentials that may have been exposed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict access to installation packages and encrypted install configuration files; rotate database and message-broker credentials; disable the optional AES-128-CBC credential protection store if not required; store secrets in an external secrets manager or vault; apply least privilege and file access controls; monitor for unauthorized access to configuration files and backups; use externally managed keys for encryption at rest; isolate affected systems and limit lateral movement.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Low
niche ICS access-control/biometric product, industry-specific not broadly deployed
Threat Intel
1
1 source
Social Media
2
Sightings
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CISA CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat Yes
Deciding rule
Active threat signals + CRITICAL/HIGH severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

53
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: +10
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Threat IntelligenceMISP

CISA Advisories
Sources: CISA (public domain)

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy