Tools / Apache Maven / Security

Security Deep Dive

Apache Maven

Security posture and CVE patch evidence from tracked releases.

Back to Tool

7 critical dependency CVEs affects maven-3.9.16.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 30d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/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 Absent

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: monthly Present

30d median over recent releases Release history

Latest release: 17d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 17d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 17d ago

Signing assets Not active yet

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

Latest release: 17d ago

4.5/10 Security Score

7.0/10 Scorecard

Dependency Exposure 18 transitive dependency CVEs found in the latest SBOM. 7 critical.

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.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

1d stale

scorecard

2.80 / 4.0

Score 7.0/10

cve health

0.00 / 2.5

No open CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 42.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

5.8

10%

supply chain risk: 42.0 transitive cves: 7c/7h

Provenance trust

provenance trust

7.0

40%

scorecard score: 7.0 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

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 42.0/100

7 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 7.0/10

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

Check	Score	Reason
Code-Review	9	Found 22/23 approved changesets -- score normalized to 9
Packaging	-1	packaging workflow not detected
Maintained	10	30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow	10	no dangerous workflow patterns detected
Binary-Artifacts	10	no binaries found in the repo
License	10	license file detected
Fuzzing	10	project is fuzzed
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
Security-Policy	10	security policy file detected
Signed-Releases	-1	no releases found
Pinned-Dependencies	3	dependency not pinned by hash detected -- score normalized to 3
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.

Dependency Vulnerabilities

700 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 (18)

Critical 7 High 7 Medium 3 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2017-1000487	critical	—	org.codehaus.plexus:plexus-utils	3.0.9	maven-3.9.16
CVE-2017-5929	critical	—	ch.qos.logback:logback-classic	—	maven-3.9.16
CVE-2019-17571	critical	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2021-26291	critical	—	org.apache.maven:maven-core	—	maven-3.9.16
CVE-2021-26291	critical	—	org.apache.maven:maven-compat	—	maven-3.9.16
CVE-2022-23305	critical	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2022-23307	critical	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2019-9843	high	—	com.diffplug.spotless:spotless-maven-plugin	—	maven-3.9.16
CVE-2021-4104	high	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2022-23302	high	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2022-4244	high	—	org.codehaus.plexus:plexus-utils	3.0.9	maven-3.9.16
CVE-2023-26464	high	—	log4j:log4j	1.2.17	maven-3.9.16
CVE-2023-6378	high	—	ch.qos.logback:logback-classic	—	maven-3.9.16
CVE-2025-67030	high	—	org.codehaus.plexus:plexus-utils	3.0.24	maven-3.9.16
CVE-2020-15250	medium	—	junit:junit	4.12	maven-3.9.16
CVE-2022-40152	medium	—	com.fasterxml.woodstox:woodstox-core	—	maven-3.9.16
CVE-2022-4245	medium	—	org.codehaus.plexus:plexus-utils	3.0.9	maven-3.9.16
CVE-2024-31573	low	—	org.xmlunit:xmlunit-core	—	maven-3.9.16

Showing 18 of 18