LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32074: HashiCorp vault-action (aka Vault GitHub Action) before 2.2.0 allows attackers to obtain sensitive informat...

HashiCorp vault-action (aka Vault GitHub Action) before 2.2.0 allows attackers to obtain sensitive information from log files because a multi-line secret was not correctly registered with GitHub Actions for log masking.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw could expose Vault-sourced multi-line secrets in GitHub Actions logs when using HashiCorp vault-action before 2.2.0. The main business risk is credential disclosure from CI logs, which may enable follow-on access if exposed secrets were valid and broadly privileged.

Executive priority

Prioritize remediation where CI logs are broadly accessible or secrets grant production, cloud, deployment, or administrative access. Treat confirmed log exposure as a credential incident requiring rotation and access review.

Technical view

HashiCorp vault-action before 2.2.0 did not correctly register multi-line secrets for GitHub Actions log masking. As a result, sensitive values could appear unmasked in workflow output. The provided sources do not include CVSS, CWE, or confirmed exploit activity.

Likely exposure

Exposure is most likely in repositories using HashiCorp vault-action versions before 2.2.0, especially workflows retrieving multi-line secrets and retaining accessible Actions logs.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Abuse depends on access to workflow logs containing unmasked multi-line secrets; the vulnerability is disclosure-oriented, not direct remote code execution.

Researcher notes

Evidence is limited to the CVE description and HashiCorp/GitHub references. No CVSS vector, CWE, CPE, or exploitation evidence is provided. Analysis should focus on action version, multi-line secret handling, log accessibility, and credential blast radius.

Mitigation direction

  • Upgrade HashiCorp vault-action to version 2.2.0 or later.
  • Review HashiCorp advisory and changelog for vendor-specific guidance.
  • Rotate any multi-line secrets that may have appeared in workflow logs.
  • Reduce GitHub Actions log retention and restrict repository log access.
  • Review Vault policies for over-privileged secrets used by CI workflows.

Validation and detection

  • Inventory workflows referencing hashicorp/vault-action and identify pinned versions.
  • Confirm all usages are pinned to 2.2.0 or later.
  • Identify workflows retrieving multi-line secrets from Vault.
  • Review historical Actions logs for unmasked secret exposure.
  • Verify rotated secrets are no longer valid in Vault and dependent systems.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32074 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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