LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26908: Automox Agent Sensitive Log Information Disclosure

Automox Agent prior to version 31 logs potentially sensitive information in local log files, which could be used by a locally-authenticated attacker to subvert an organization's security program. The issue has since been fixed in version 31 of the Automox Agent.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Automox Agent before version 31 could write potentially sensitive information into local log files. A person who already has authenticated local access to an affected endpoint might read those logs and use the information against the organization’s security operations. The vendor states the issue was fixed in Agent version 31.

Executive priority

Treat this as a low-severity cleanup item, not an emergency. It still matters because endpoint management logs can expose security-relevant information after an attacker gains local access. Remediate during normal vulnerability management cycles unless sensitive log exposure is confirmed.

Technical view

This is a CWE-532 sensitive-information-in-log-files issue in Automox Agent. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, unchanged scope, and low confidentiality impact only. The provided affected data names Automox Agent version 30, with the description stating versions prior to 31 were affected.

Likely exposure

Exposure is limited to endpoints running Automox Agent prior to version 31, especially version 30 as listed in the source bundle. An attacker needs local authenticated access to the machine before the log disclosure matters.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The attack context is post-access: a local authenticated user may read sensitive log content and use it to undermine security operations.

Researcher notes

The evidence supports local authenticated information disclosure only. Do not expand scope beyond Automox Agent prior to version 31. The provided sources identify the fix as version 31 and do not provide evidence of remote exploitation, privilege escalation, or active exploitation.

Mitigation direction

  • Upgrade Automox Agent to version 31 or later.
  • Prioritize endpoints still running Agent version 30 or older.
  • Restrict local access to Automox Agent log files.
  • Review affected logs for sensitive information exposure.
  • Follow Automox guidance for any additional cleanup steps.

Validation and detection

  • Inventory deployed Automox Agent versions across endpoints.
  • Confirm no endpoint remains below Agent version 31.
  • Review local agent logs for exposed sensitive values.
  • Verify upgraded agents no longer log the sensitive data.
  • Document any discovered exposure and response actions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-532: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-26908 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2021-26908Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AutomoxAutomox Agent30Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.