Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain read access to broker log or support bundle
-
ExploitLocate plaintext client credential entry
-
ExecutionExtract logged username and password
-
ImpactReuse credential to authenticate to broker/devices
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Exploitation Conditions | Exploitation requires read access to the Armatura One message broker's operational log file, or to any backup archive or diagnostic/support bundle that includes that log - the credentials and password are written there in plain text during normal operation, so no special product feature must be enabled. Limiting factors: the attack is local (AV:L), not network-exploitable, meaning the attacker must already be able to read the host filesystem or obtain an exported log/backup/support bundle; risk is amplified in practice when support bundles are shared with the vendor or third parties, since that extends who can read the credential beyond the host itself. |
| Impact | This is a low-to-moderate priority issue whose real-world risk is constrained by the local attack vector. The provided CVSS:3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 4.0) indicates a local, low-complexity attack affecting confidentiality only, with no integrity or availability impact - consistent with a CWE-532 plaintext-credential-in-logs weakness. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so exploitation status is 'no public exploit identified at time of analysis'; this flaw is not a candidate for mass automated exploitation because it requires access to the log, backup, or support bundle first. One tension worth flagging: the CVSS vector sets PR:N (no privileges), yet the description states exploitation requires 'read access to this log, or to a backup or support bundle' - obtaining that read access generally implies some level of local access or privilege, so PR:N arguably understates the precondition and should be verified against the vendor advisory. The logged credential also enables follow-on lateral movement (the harvested password may unlock the message broker or connected devices), so impact may be understated as C:L if the exposed credential is high-value. Overall: a defense-in-depth hardening fix rather than an urgent emergency, but relevant in OT/ICS environments where support bundles are routinely shared with vendors. |
| Exploit ScenarioDerived | An attacker or insider with read access to the Armatura One host filesystem, or someone who receives a diagnostic/support bundle or backup archive, opens the message broker log and reads the client connection credentials and password stored in plain text. No public exploit code is needed - the credential is simply present in the log and can be reused to authenticate to the broker or connected systems. Because the CVSS vector is AV:L, this requires local or equivalent access to the log data rather than a remote network request. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Cleartext credential disclosure in the Armatura One message broker causes client connection credentials and their associated passwords to be written to the broker's operational log in plain text during normal operation, so anyone who can read that log - or a backup or diagnostic/support bundle containing it - obtains a usable credential. The exposure is local rather than network-reachable: per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) an attacker must already have low-privileged read access to the host filesystem or to an exported log, backup, or support bundle, and there is no public exploit identified at time of analysis. Assignment of CWE-532 means the credential never needs to be decrypted or brute-forced; the weakness is simply that the protocol exchanges are logged verbatim, which is why this is rated a low-to-moderate priority issue whose practical blast radius depends on how widely logs and support bundles are copied and shared.
RemediationAI
No vendor-released patch was identified in the available intelligence for CVE-2026-94594, so treat patch status as unconfirmed and consult CISA ICS advisory ICSA-26-274-01 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-274-01) for the vendor's current guidance before assuming an update removes the logging behavior. Until a fix is confirmed, treat every broker credential that may have transited the affected log as compromised: rotate client connection passwords for the message broker and any downstream integration that reused them, and invalidate cached or stored copies. Tighten the log artifact itself - restrict the broker log directory and rotated logs to the service account and a minimal admin group (for example root:armatura with 0600/0640 permissions), verify that file ACLs are not widened by the installer, and confirm no world-readable or group-readable log path exists. Enforce the same controls on backups: encrypt backup archives at rest, restrict restore access, and purge historical archives that predate the rotation, accepting the trade-off that shorter retention reduces forensic and troubleshooting history. Before any support bundle or diagnostic export leaves the site, redact or strip broker logs containing connection lines, and use a controlled transfer channel; the trade-off is that redaction can slow vendor troubleshooting and some vendors may request unredacted logs, in which case a confidentiality agreement plus a dedicated staging copy is safer than sending production logs. If the broker exposes a logging verbosity or credential-logging switch, lower it to a level that omits authentication exchanges and re-verify after restart; the side effect is reduced diagnostic fidelity for connection failures, so compensate with authentication failure counters or broker-side audit events. Finally, monitor and alert on reads of the broker log path and on new copies of log files appearing outside the log directory, since that activity is the practical detection signal for this class of disclosure.
Affected VersionsENISA
Affected Packages
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 affected component is the message broker embedded in Armatura One, an Armatura LLC physical security and access-control platform (CISA ICS advisory ICSA-26-274-01, published under the ICS program). Message brokers authenticate clients - readers, controllers, panels, and management integrations - by exchanging a client identifier plus a password or shared secret, and in Armatura One those connection parameters are emitted to the broker's operational log at a verbosity level used during normal operation rather than only in a debug mode. That behavior is the textbook instance of CWE-532, Insertion of Sensitive Information into Log File: the application materializes a secret into a durable, broadly readable artifact whose access controls are typically weaker than those protecting the credential store, and whose copies multiply through backups, log shipping, and vendor support bundles. The disclosed items are credentials for connecting to the broker, so possession of the log is effectively possession of the credential, enabling an attacker to impersonate a legitimate broker client rather than merely to learn configuration details. The CPE data identifies both cpe:2.3:a:armatura_llc:armatura_one and cpe:2.3:a:armatura_llc:armatura_one_(usa) with wildcard version fields, indicating the vendor did not scope a fixed version range in the advisory. The assessed attack prerequisites are local (AV:L) with low privileges (PR:L), no user interaction, and a confidentiality-only impact on the credential itself, which is consistent with an information-disclosure logging defect rather than a remotely triggerable compromise; the original NVD-style vector supplied with the record differs on privilege and confidentiality weighting, and the independent assessment should be treated as authoritative.
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
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Reading the broker log requires local access and typically some privilege (PR:L); a fully exposed reusable credential justifies C:H, with no integrity or availability impact.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
2DescriptionCVE.org
Armatura One's message broker logs client connection credentials and the associated password in plain text during normal operation. Any party with read access to this log, or to a backup or support bundle that includes it, can obtain the logged credential.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Armatura One
View allArmatura One ships with a fixed, vendor-defined password assigned to its database superuser account during database init
Armatura One and Armatura One (USA) installations that enable the optional AES-128-CBC credential protection store datab
Armatura One's backup and restore routine writes the complete database connection command - including the database super
EUVD-2026-91830
GHSA-cmfx-346m-p68q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB