Security Deep Dive
Jenkins
Security posture and CVE patch evidence from tracked releases.
No known vulnerabilities in jenkins-2.565.
5 CVEs patched in tracked history.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| jenkins-2.565 | 2026-05-20 | — | — | — | — | — |
Latest
|
| jenkins-2.555.2 | 2026-05-13 | — | — | — | — | — |
—
|
| jenkins-2.564 | 2026-05-12 | — | — | — | — | — |
Patches
CVE-2015-5317
Patches
CVE-2017-1000353
Patches
CVE-2018-1000861
Patches
CVE-2021-39144
Patches
CVE-2024-23897
|
| jenkins-2.563 | 2026-05-05 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.562 | 2026-04-28 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.561 | 2026-04-21 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.560 | 2026-04-21 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.555.1 | 2026-04-15 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.559 | 2026-04-14 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.558 | 2026-04-07 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.557 | 2026-03-31 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.556 | 2026-03-24 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.555 | 2026-03-18 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.541.3 | 2026-03-18 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.554 | 2026-03-10 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.553 | 2026-03-03 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.552 | 2026-02-24 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.551 | 2026-02-18 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.541.2 | 2026-02-18 | 3 | 2 | — | — | KEV 5 |
—
|
| jenkins-2.550 | 2026-02-10 | 3 | 2 | — | — | KEV 5 |
—
|
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
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.945
freshness
1.00 / 1.0
1d stale
scorecard
2.20 / 4.0
Score 5.5/10
cve health
0.00 / 2.5
⚠ No direct scan — 27c/95h 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 v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
5.5
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
0.0
10%
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/100Scorecard
Scorecard 5.5/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 5 | Found 7/12 approved changesets -- score normalized to 5 |
| Packaging | -1 | packaging workflow not detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| CII-Best-Practices | 5 | badge detected: Passing |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Security-Policy | 10 | security policy file detected |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Pinned-Dependencies | 9 | dependency not pinned by hash detected -- score normalized to 9 |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
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
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| CVE-2015-5317 | HIGH | 97%ile | — | jenkins-2.564 | — | — | KEV |
| CVE-2017-1000353 | CRITICAL | 99%ile | — | jenkins-2.564 | — | — | KEV |
| CVE-2018-1000861 | CRITICAL | 100%ile | — | jenkins-2.564 | — | — | KEV |
| CVE-2021-39144 | HIGH | 99%ile | — | jenkins-2.564 | — | — | KEV |
| CVE-2024-23897 | CRITICAL | 99%ile | — | jenkins-2.564 | — | — | KEV |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
0
Medium
0
Low
0
Unknown
0
No dependency CVEs match this filter.
Showing 0 of 320