How severe is CVE-2025-4057?

CVE-2025-4057 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-4057?

CVE-2025-4057 affects the following packages: github.com/arkmq-org/activemq-artemis-operator (Go). Ecosystems affected: Go.

How do I fix CVE-2025-4057?

The records we use list no patched version of github.com/arkmq-org/activemq-artemis-operator for CVE-2025-4057. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2025-4057 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/arkmq-org/activemq-artemis-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-4057 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-4057 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-4057 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-4057?

CVE-2025-4057 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-4057?

CVE-2025-4057 is classified as CWE-1391 (CWE-1391). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-4057 published, and has it been updated?

CVE-2025-4057 was published on May 26, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2025-4057 — activemq-artemis-operator

MEDIUMFix: arkmq-org/activemq-artemis-operator@d3482fa

CVE-2025-4057 is a medium-severity (CVSS 5.5) CWE-1391 vulnerability in github.com/arkmq-org/activemq-artemis-operator. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Activemq-artemis-operator: amq broker operator starting credentials reuse

Also known asGHSA-q5q7-8x6x-hcg2GO-2025-3717

Published

May 26, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-4057.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/arkmq-org/activemq-artemis-operator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/arkmq-org/activemq-artemis-operator`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/arkmq-org/activemq-artemis-operator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/arkmq-org/activemq-artemis-operator for CVE-2025-4057. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
AMQ Broker 7.13.0.OPR.1.GA	`activemq-artemis-operator`	RHSA-2025:8147
Red Hat AMQ Broker 7.12.5	`activemq-artemis-operator`	RHSA-2025:12473
RHEL-8 based Middleware Containers	`amq7/amq-broker-init-rhel8:7.12.5-2`	RHSA-2025:12355

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2025-4057 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works