Tools / LibreNMS / Security

Security Deep Dive

LibreNMS

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects 26.5.1.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 13d 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

13d median over recent releases Release history

Latest release: 14d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 14d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 14d ago

Signing assets Not active yet

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

Latest release: 14d ago

4.9/10 Security Score

5.3/10 Scorecard

Dependency Exposure 26 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

Up to date

scorecard

2.12 / 4.0

Score 5.3/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 30.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

6.9

10%

supply chain risk: 30.65 transitive cves: 1c/13h

Provenance trust

provenance trust

5.3

40%

scorecard score: 5.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

68% Dependency freshness

Scorecard

Scorecard 5.3/10

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

Check	Score	Reason
Maintained	10	30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Packaging	-1	packaging workflow not detected
Code-Review	7	Found 21/30 approved changesets -- score normalized to 7
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	5	badge detected: Passing
Fuzzing	0	project is not fuzzed
License	9	license file detected
Signed-Releases	-1	no releases found
Branch-Protection	0	branch protection not enabled on development/release branches
Binary-Artifacts	10	no binaries found in the repo
SAST	0	SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

Dependency Vulnerabilities

493 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 (20) All (26)

Critical 1 High 13 Medium 10 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-36039	critical	—	pymysql	1.0.0 \|\| > 1.0.0	26.5.0
CVE-2013-1633	high	—	setuptools	—	26.5.0
CVE-2022-40897	high	—	setuptools	—	26.5.0
CVE-2024-6345	high	—	setuptools	—	26.5.0
CVE-2025-47273	high	—	setuptools	—	26.5.0
CVE-2026-40176	high	—	composer/composer	2.9.5	26.5.0
CVE-2026-40261	high	—	composer/composer	2.9.5	26.5.0
CVE-2026-42033	high	—	axios	1.15.0	26.5.0
CVE-2026-42035	high	—	axios	1.15.0	26.5.0
CVE-2026-42043	high	—	axios	1.15.0	26.5.0
CVE-2026-42264	high	—	axios	1.15.0	26.5.0
CVE-2026-44167	high	—	phpseclib/phpseclib	3.0.51	26.5.0
CVE-2026-6321	high	—	fast-uri	3.1.0	26.5.0
CVE-2026-6322	high	—	fast-uri	3.1.0	26.5.0
CVE-2024-6783	medium	—	vue-template-compiler	2.7.16	26.5.0
CVE-2026-28684	medium	—	python-dotenv	—	26.5.0
CVE-2026-42034	medium	—	axios	1.15.0	26.5.0
CVE-2026-42036	medium	—	axios	1.15.0	26.5.0
CVE-2026-42037	medium	—	axios	1.15.0	26.5.0
CVE-2026-42038	medium	—	axios	1.15.0	26.5.0
CVE-2026-42039	medium	—	axios	1.15.0	26.5.0
CVE-2026-42041	medium	—	axios	1.15.0	26.5.0
CVE-2026-42042	medium	—	axios	1.15.0	26.5.0
CVE-2026-42044	medium	—	axios	1.15.0	26.5.0
CVE-2024-9506	low	—	vue	2.7.16	26.5.0
CVE-2026-42040	low	—	axios	1.15.0	26.5.0

Showing 26 of 26