NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2020-10727 — artemis-commons

MEDIUM

CVE-2020-10727 is a medium-severity (CVSS 5.5) CWE-312 vulnerability in org.apache.activemq:artemis-commons. A fix is available for org.apache.activemq:artemis-commons — see the affected versions and patch details below.

ActiveMQ Artemis has Insufficiently Protected Credentials

Also known asGHSA-q9g8-9hpp-xc82
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.19%0.53%0.86%1.20%0.7%0.7%Jul 26Oct 26Nov 26

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
☕org.apache.activemq:artemis-commons

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

Description

A flaw was found in ActiveMQ Artemis management API from version 2.7.0 up until 2.12.0, where a user inadvertently stores passwords in plaintext in the Artemis shadow file (etc/artemis-users.properties file) when executing the resetUsers operation. A local attacker can use this flaw to read the contents of the Artemis shadow file.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.activemq:artemis-commons≥ 2.7.0&&< 2.13.02.13.0org.apache.activemq:artemis-commons:2.13.0

Affected Products

2 products · 2 configurations
Application
artemisapache
≥ 2.7.0 && ≤ 2.12.0
range
Application
oncommand workflow automationnetapp
all

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update org.apache.activemq:artemis-commons to 2.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10727 is resolved across your whole dependency graph.

  3. Workarounds

    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
Workaround published by Red Hat
When resetting a user an alternative is to use the broker instance CLI `/bin/artemis user reset` which is not affected by the flaw
Source: Red Hat security advisory for CVE-2020-10727 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat AMQsee advisoryRHSA-2020:3133
Red Hat AMQbrokerRHSA-2020:2751

Frequently Asked Questions

A flaw was found in ActiveMQ Artemis management API from version 2.7.0 up until 2.12.0, where a user inadvertently stores passwords in plaintext in the Artemis shadow file (etc/artemis-users.properties file) when executing the `resetUsers` operation. A local attacker can use this flaw to read the contents of the Artemis shadow file.
O3 Security · Impact-Aware SCA

Is CVE-2020-10727 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-10727: artemis-commons — Fixed in 2.13.0