# CVE-2024-23840: `goreleaser release --debug` shows secrets

> Enabling debug mode in GoReleaser exposes secret values in logs, allowing attackers with log access to steal sensitive credentials.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** GHSA-h3q2-8whx-c29h, GO-2024-2482

## What is CVE-2024-23840?

CVE-2024-23840 is a medium-severity vulnerability in goreleaser, published on 30 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-23840?

3 open source packages ship an affected version, including github.com/goreleaser/goreleaser. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/goreleaser/goreleaser` | Go | From 1.23.0 | 1.24.0 |
| `github.com/goreleaser/goreleaser` | Go | From 1.23.0 | 1.24.0 |
| `github.com/goreleaser/goreleaser` | Go | From 1.23.0 | 1.24.0 |

Products: Goreleaser Goreleaser.

## How do I fix CVE-2024-23840?

Upgrade github.com/goreleaser/goreleaser to 1.24.0 or later.

## Is CVE-2024-23840 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23840 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23840 and fix it if it is affected.

What it is: CVE-2024-23840 is a medium-severity vulnerability in goreleaser, published on 30 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23840 exists.

Affected packages and fixed versions:
- github.com/goreleaser/goreleaser (Go): affected from 1.23.0; fixed in 1.24.0
- github.com/goreleaser/goreleaser (Go): affected from 1.23.0; fixed in 1.24.0
- github.com/goreleaser/goreleaser (Go): affected from 1.23.0; fixed in 1.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23840/ (Markdown: https://insights.sbomify.com/CVE-2024-23840/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23840
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23840
- OSV: https://osv.dev/vulnerability/CVE-2024-23840

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23840/
Summaries are generated and may contain mistakes; the official description above is the record.