Skip to content
Tools / ArgoCD / Security

Security Deep Dive

ArgoCD

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v3.4.5.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 1d 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: 14d ago
Release cadence: weekly Present
1d median over recent releases Release history
Latest release: 17d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 8d 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
6.1/10 Security Score
8.4/10 Scorecard
Dependency Exposure 67 transitive dependency CVEs found in the latest SBOM. 1 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

3.36 / 4.0

Score 8.4/10

cve health

1.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 60.8/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

3.9

10%

supply chain risk: 60.8 transitive cves: 1c/28h

Provenance trust

provenance trust

8.4

40%

scorecard score: 8.4 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 60.8/100
1 Transitive critical CVEs
0 KEV-transitive CVEs
60% Dependency freshness

Scorecard

Scorecard 8.4/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
Dependency-Update-Tool 10 update tool detected
Security-Policy 10 security policy file detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Token-Permissions 10 GitHub workflow tokens follow principle of least privilege
Binary-Artifacts 10 no binaries found in the repo
CII-Best-Practices 5 badge detected: Passing
Signed-Releases 10 5 out of the last 5 releases have a total of 5 signed artifacts.
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
Fuzzing 0 project is not fuzzed
License 10 license file detected
Pinned-Dependencies 7 dependency not pinned by hash detected -- score normalized to 7
Vulnerabilities 0 27 existing vulnerabilities detected
Packaging 10 packaging workflow detected
SAST 9 SAST tool detected but not run on all commits
CI-Tests 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 43 contributing companies or organizations

Dependency Vulnerabilities

1708 dependencies scanned View full dependency list →

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

Critical

1

High

28

Medium

26

Low

7

Unknown

5

Still affecting latest (36) All (67)
Critical 1 High 28 Medium 26 Low 7 Unknown 5
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-25896 critical — fast-xml-parser 4.5.3 v3.4.2
CVE-2025-12816 high — node-forge 1.3.1 v3.4.2
CVE-2025-66031 high — node-forge 1.3.1 v3.4.2
CVE-2026-23745 high — tar 6.2.1 v3.4.2
CVE-2026-23950 high — tar 6.2.1 v3.4.2
CVE-2026-24842 high — tar 6.2.1 v3.4.2
CVE-2026-26278 high — fast-xml-parser 4.5.3 v3.4.2
CVE-2026-26960 high — tar 6.2.1 v3.4.2
CVE-2026-26996 high — minimatch 5.1.6 v3.4.2
CVE-2026-27903 high — minimatch 5.1.7 v3.4.2
CVE-2026-27904 high — minimatch 5.1.7 v3.4.2
CVE-2026-29063 high — immutable 5.1.3 v3.4.2
CVE-2026-29181 high — go.opentelemetry.io/otel v1.38.0 v3.4.2
CVE-2026-29786 high — tar 6.2.1 v3.4.2
CVE-2026-31802 high — tar 6.2.1 v3.4.2
CVE-2026-32141 high — flatted 3.3.3 v3.4.2
CVE-2026-33036 high — fast-xml-parser 4.5.3 v3.4.2
CVE-2026-33228 high — flatted 3.3.3 v3.4.2
CVE-2026-33671 high — picomatch 2.3.1 v3.4.2
CVE-2026-33891 high — node-forge 1.3.1 v3.4.2
CVE-2026-33894 high — node-forge 1.3.1 v3.4.2
CVE-2026-33895 high — node-forge 1.3.1 v3.4.2
CVE-2026-33896 high — node-forge 1.3.1 v3.4.2
CVE-2026-35469 high — github.com/moby/spdystream v0.5.0 v3.4.2
CVE-2026-44728 high — @babel/plugin-transform-modules-systemjs 7.27.1 v3.4.2
CVE-2026-4867 high — path-to-regexp 0.1.12 v3.4.2
CVE-2026-6321 high — fast-uri 3.0.6 v3.4.2
CVE-2026-6322 high — fast-uri 3.0.6 v3.4.2
GHSA-5c6j-r48x-rmvq high — serialize-javascript 5.0.1 v3.4.2
CVE-2025-15284 medium — qs 6.13.0 v3.4.2
CVE-2025-15599 medium — dompurify 3.2.6 v3.4.2
CVE-2025-30359 medium — webpack-dev-server 4.15.2 v3.4.2
CVE-2025-30360 medium — webpack-dev-server 4.15.2 v3.4.2
CVE-2025-64718 medium — js-yaml 3.14.1 v3.4.2
CVE-2025-66030 medium — node-forge 1.3.1 v3.4.2
CVE-2025-69873 medium — ajv 7.2.4 v3.4.2
CVE-2026-0540 medium — dompurify 3.2.6 v3.4.2
CVE-2026-25934 medium — github.com/go-git/go-git/v5 v5.14.0 v3.4.2
CVE-2026-33349 medium — fast-xml-parser 4.5.3 v3.4.2
CVE-2026-33672 medium — picomatch 2.3.1 v3.4.2
CVE-2026-33750 medium — brace-expansion 2.0.2 v3.4.2
CVE-2026-34043 medium — serialize-javascript 5.0.1 v3.4.2
CVE-2026-34165 medium — github.com/go-git/go-git/v5 v5.14.0 v3.4.2
CVE-2026-41238 medium — dompurify 3.2.6 v3.4.2
CVE-2026-41239 medium — dompurify 3.2.6 v3.4.2
CVE-2026-41240 medium — dompurify 3.2.6 v3.4.2
CVE-2026-41305 medium — postcss 8.4.49 v3.4.2
CVE-2026-41506 medium — github.com/go-git/go-git/v5 v5.14.0 v3.4.2
CVE-2026-41650 medium — fast-xml-parser 4.5.3 v3.4.2
GHSA-39q2-94rc-95cp medium — dompurify 3.2.6 v3.4.2
GHSA-67mh-4wv8-2f99 medium — esbuild 0.18.20 v3.4.2
GHSA-cj63-jhhr-wcxv medium — dompurify 3.2.6 v3.4.2
GHSA-cjmm-f4jc-qw8r medium — dompurify 3.2.6 v3.4.2
GHSA-h8r8-wccr-v5f2 medium — dompurify 3.2.6 v3.4.2
GHSA-r4q5-vmmm-2653 medium — follow-redirects 1.15.9 v3.4.2
CVE-2026-2391 low — qs 6.13.0 v3.4.2
CVE-2026-24001 low — diff 4.0.2 v3.4.2
CVE-2026-27942 low — fast-xml-parser 4.5.3 v3.4.2
CVE-2026-33762 low — github.com/go-git/go-git/v5 v5.14.0 v3.4.2
CVE-2026-3449 low — @tootallnate/once 2.0.0 v3.4.2
CVE-2026-4539 low — pygments 2.19.2 v3.4.2
GHSA-xffm-g5w8-qvg7 low — @eslint/plugin-kit 0.3.3 v3.4.2
CVE-2024-7598 unknown — k8s.io/kubernetes v1.34.2 v3.4.2
CVE-2025-1767 unknown — k8s.io/kubernetes v1.34.2 v3.4.2
CVE-2025-47911 unknown — golang.org/x/net v0.44.0 v3.4.2
CVE-2025-58190 unknown — golang.org/x/net v0.44.0 v3.4.2
CVE-2026-33814 unknown — golang.org/x/net v0.44.0 v3.4.2

Showing 67 of 67

Beta — feedback welcome: [email protected]