# CVE-2025-4057: Activemq-artemis-operator: amq broker operator starting credentials reuse

> The ActiveMQ Artemis operator reuses generated passwords across separate custom resources, allowing attackers to access multiple brokers with the same 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:** 26 May 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-q5q7-8x6x-hcg2, GO-2025-3717

## What is CVE-2025-4057?

CVE-2025-4057 is a medium-severity vulnerability in Red Hat AMQ Broker 7.13.0.OPR.1.GA, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in ActiveMQ Artemis. The password generated by activemq-artemis-operator does not regenerate between separated CR dependencies.

Weakness: CWE-1391 (Use of Weak Credentials)

## Which versions are affected by CVE-2025-4057?

3 open source packages ship an affected version, including github.com/arkmq-org/activemq-artemis-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/arkmq-org/activemq-artemis-operator` | Go | All versions | None |
| `github.com/arkmq-org/activemq-artemis-operator` | Go | All versions to 0.0.0-20250418141202-b262048e6a75 | None |
| `github.com/arkmq-org/activemq-artemis-operator` | Go | All versions to 0.0.0-20250418141202-b262048e6a75 | None |

## How do I fix CVE-2025-4057?

Apply the vendor's patch.

## Is CVE-2025-4057 being exploited?

There is no known exploitation of CVE-2025-4057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4057 and fix it if it is affected.

What it is: CVE-2025-4057 is a medium-severity vulnerability in Red Hat AMQ Broker 7.13.0.OPR.1.GA, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4057 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/arkmq-org/activemq-artemis-operator (Go): affected all versions; no fix listed
- github.com/arkmq-org/activemq-artemis-operator (Go): affected all versions up to 0.0.0-20250418141202-b262048e6a75; no fix listed
- github.com/arkmq-org/activemq-artemis-operator (Go): affected all versions up to 0.0.0-20250418141202-b262048e6a75; no fix listed

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-2025-4057/ (Markdown: https://insights.sbomify.com/CVE-2025-4057/index.md)
```

## Sources

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

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