CVE Intelligence
Skip to main content
mediumInfo Disclosurepublic exploit

CVE-2026-94594

CVE-2026-94594 — Armatura LLC Armatura One Insertion of Sensitive Information into Log File

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.

Published Updated Sources: NVD, Armatura LLC (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

Armatura LLC

4 products listed

CVSS base

4

medium · 2 sources

Remediation

The vendor's own words where we have them.

Armatura LLC has released Armatura One V4.7.2, which resolves this issue. Users should upgrade from V4.7.1 or earlier to V4.7.2. Armatura LLC has released Armatura One V4.6.1_USA, which resolves this issue. Users of the USA release line should upgrade from V4.3.1_USA or earlier to V4.6.1_USA. Armatura LLC recommends contacting official technical support for guidance on obtaining and applying the upgrade.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
Armatura LLCArmatura One0 to < 4.7.2Vulnerable
Armatura LLCArmatura One4.7.2Patched
Armatura LLCArmatura One (USA)0 to < 4.6.1Vulnerable
Armatura LLCArmatura One (USA)4.6.1_USAPatched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4CVSS 3.1medium2.51.4hq.dhs.gov (CNA), Armatura LLC (CNA)
5.1CVSS 4.0medium——Armatura LLC (CNA)

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-532 · Insertion of Sensitive Information into Log File

  • Read Application Data

Mitigation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.

Weakness & attack patterns

  • CWE-532

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-215 · Fuzzing and observing application log data/errors for application mapping

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 4.0 (AV:L)

    Oct 2, 2026 · NVD

  3. Initial · CVE published

    Oct 2, 2026 · NVD

  4. CVE published by MITRE.

    Oct 2, 2026 · SOCRadar CTI

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-94594 is Armatura LLC Armatura One Insertion of Sensitive Information into Log File, a medium vulnerability affecting Armatura One, Armatura One (USA) from Armatura LLC. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-94594. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.