Skip to content
Tools / clamav / Security

Security Deep Dive

clamav

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 high-severity dependency CVEs affects clamav-1.5.3.

Review the dependency vulnerabilities below.

— 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: 14d ago
Release cadence: weekly Present
0d median over recent releases Release history
Latest release: 25d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 16d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 25d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 25d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 25d ago
5.1/10 Security Score
6.8/10 Scorecard
Dependency Exposure 13 transitive dependency CVEs found in the latest SBOM.

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

9d stale

scorecard

2.72 / 4.0

Score 6.8/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/5h transitive 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.11 / 10.0

Risk 11.1/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

8.9

10%

supply chain risk: 11.08 transitive cves: 0c/5h

Provenance trust

provenance trust

6.8

40%

scorecard score: 6.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 9d

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 11.1/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
46% Dependency freshness

Scorecard

Scorecard 6.8/10

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

Check Score Reason
Packaging -1 packaging workflow not detected
Code-Review 6 Found 17/27 approved changesets -- score normalized to 6
Maintained 10 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Security-Policy 10 security policy file detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
License 10 license file detected
Binary-Artifacts 6 binaries present in source code
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 10 project is fuzzed
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Signed-Releases 8 5 out of the last 5 releases have a total of 5 signed artifacts.
SAST 9 SAST tool detected but not run on all commits

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

335 dependencies scanned View full dependency list →

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

Critical

0

High

5

Medium

4

Low

2

Unknown

2

High 5 Medium 4 Low 2 Unknown 2
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-41676 high openssl 0.10.73 clamav-1.4.5
CVE-2026-41678 high openssl 0.10.73 clamav-1.4.5
CVE-2026-41681 high openssl 0.10.73 clamav-1.4.5
CVE-2026-41898 high openssl 0.10.73 clamav-1.4.5
CVE-2026-42327 high openssl 0.10.73 clamav-1.4.5
CVE-2026-25541 medium bytes 1.10.1 clamav-1.4.5
CVE-2026-33055 medium tar 0.4.44 clamav-1.4.5
CVE-2026-33056 medium tar 0.4.44 clamav-1.4.5
CVE-2026-44662 medium openssl 0.10.73 clamav-1.4.5
CVE-2026-41677 low openssl 0.10.73 clamav-1.4.5
GHSA-cq8v-f236-94qc low rand 0.8.5 clamav-1.4.5
RUSTSEC-2024-0436 unknown paste 1.0.15 clamav-1.4.5
RUSTSEC-2026-0097 unknown rand 0.8.5 clamav-1.4.5

Showing 13 of 13

Beta — feedback welcome: [email protected]