Credential Secrets Exposed in Execution Error Data of Several Nodes
Résumé
Impact
When an operation failed, the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes stored an error that contained a secret from their credential: a Git password or token, a MongoDB database password, or a Google access token. A user who can view the workflow's executions, but...
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| npm | n8n |
< 1.123.85 |
>= 1.123.85 |
| npm | n8n |
< 2.44.1 |
>= 2.44.1 |
| npm | n8n |
< 2.43.5 |
>= 2.43.5 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
Impact
When an operation failed, the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes stored an error that contained a secret from their credential: a Git password or token, a MongoDB database password, or a Google access token. A user who can view the workflow's executions, but cannot read the credential, could recover the secret from the execution data.
Patches
The issue has been fixed in n8n versions 1.123.85, 2.44.1, and 2.43.5. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Limit execution read access to the minimum set of users who require it.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Source: GitHub Repository Security Advisories (Game のスタック) GitHub Advisory OSV
Références
- GITHUB_REPO_ADVISORY n8n-io/n8n