Tools / ActiveMQ / Security

Security Deep Dive

ActiveMQ

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No known vulnerabilities in activemq-5.19.7.

8 CVEs patched in tracked history.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

10 versions tracked

Version	Published	C	H	M	L	KEV	Notes
activemq-5.19.7	2026-05-27	—	—	—	—	—	Latest
activemq-6.2.6	2026-05-27	—	—	—	—	—	Patches CVE-2016-3088 Patches CVE-2016-4437 Patches CVE-2021-39144 Patches CVE-2021-44228 Patches CVE-2021-45046 Patches CVE-2022-22965 Patches CVE-2023-46604 Patches CVE-2026-34197
activemq-5.19.6	2026-04-21	6	2	—	—	KEV 8	—
activemq-6.2.5	2026-04-21	6	2	—	—	KEV 8	—
activemq-5.19.5	2026-04-08	6	2	—	—	KEV 8	—
activemq-6.2.4	2026-04-08	6	2	—	—	KEV 8	—
activemq-5.19.4	2026-03-28	6	2	—	—	KEV 8	—
activemq-6.2.3	2026-03-27	6	2	—	—	KEV 8	—
activemq-5.19.3	2026-03-20	6	2	—	—	KEV 8	—
activemq-6.2.2	2026-03-20	6	2	—	—	KEV 8	—

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 0d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: weekly Present

0d median over recent releases Release history

Latest release: 7d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 7d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 7d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 7d ago

1.0/10 Security Score

6.3/10 Scorecard

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.00 / 0.5

Max EPSS 0.944

freshness

1.00 / 1.0

4d stale

scorecard

2.52 / 4.0

Score 6.3/10

cve health

0.00 / 2.5

⚠ No direct scan — 66c/151h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

-1.50 / 1.5

KEV exposure detected

supply chain risk

-1.50 / 10.0

Risk 100.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

0.0

10%

supply chain risk: 100.0 transitive cves: 66c/151h

Provenance trust

provenance trust

6.3

40%

scorecard score: 6.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 4d

Operational risk

operational risk

0.0

10%

kev exposure: detected epss max: 0.944

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 100.0/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 6.3/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Code-Review	10	all changesets reviewed
Maintained	10	30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
Security-Policy	10	security policy file detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Token-Permissions	8	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	3	binaries present in source code
Packaging	-1	packaging workflow not detected
License	10	license file detected
Signed-Releases	-1	no releases found
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0
Fuzzing	0	project is not fuzzed
SAST	0	SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

CVE Patch History

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low

2026

CVE	Severity	EPSS	Disclosed	Fixed in	Days to fix	vs Ecosystem Median	KEV
CVE-2016-3088	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2016-4437	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2021-39144	HIGH	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2021-44228	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2021-45046	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2022-22965	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2023-46604	CRITICAL	99%ile	—	activemq-6.2.6	—	—	KEV
CVE-2026-34197	HIGH	99%ile	—	activemq-6.2.6	—	—	KEV

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

343 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (0) All (359)

No dependency CVEs match this filter.

Showing 0 of 359