Tools / roundcubemail / Security

Security Deep Dive

roundcubemail

Security posture and CVE patch evidence from tracked releases.

Back to Tool

6 high-severity dependency CVEs affects 1.7.1.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 5d 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: 21d ago

Release cadence: weekly Present

5d median over recent releases Release history

Latest release: 10d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 3d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 10d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 10d ago

Signing assets Not active yet

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

Latest release: 10d ago

5.9/10 Security Score

6.1/10 Scorecard

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

2d stale

scorecard

2.44 / 4.0

Score 6.1/10

cve health

1.50 / 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.30 / 10.0

Risk 13.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

6.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.7

10%

supply chain risk: 12.99 transitive cves: 0c/6h

Provenance trust

provenance trust

6.1

40%

scorecard score: 6.1 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

51% Dependency freshness

Scorecard

Scorecard 6.1/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

242 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 (19)

High 6 Medium 13

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-51736	high	—	symfony/process	6.4,< 7.0 \|\| >= 7.0,< 8.0	1.7.0
CVE-2026-24765	high	—	phpunit/phpunit	10.5.47,< 11.0.0 \|\| >= 11.0,< 12.0	1.7.0
CVE-2026-27606	high	—	rollup	4.45.1	1.7.0
CVE-2026-33671	high	—	picomatch	4.0.3	1.7.0
CVE-2026-4800	high	—	lodash	4.17.21	1.7.0
GHSA-5c6j-r48x-rmvq	high	—	serialize-javascript	6.0.2	1.7.0
CVE-2022-24953	medium	—	pear/crypt_gpg	1.6.3	1.7.0
CVE-2024-29203	medium	—	tinymce	5.10.9	1.7.0
CVE-2024-29881	medium	—	tinymce	5.10.9	1.7.0
CVE-2024-38356	medium	—	tinymce	5.10.9	1.7.0
CVE-2024-38357	medium	—	tinymce	5.10.9	1.7.0
CVE-2025-13465	medium	—	lodash	4.17.21	1.7.0
CVE-2025-46734	medium	—	league/commonmark	2.7,< 3.0	1.7.0
CVE-2026-2327	medium	—	markdown-it	14.1.0	1.7.0
CVE-2026-2950	medium	—	lodash	4.17.21	1.7.0
CVE-2026-30838	medium	—	league/commonmark	2.7,< 3.0	1.7.0
CVE-2026-33347	medium	—	league/commonmark	2.7,< 3.0	1.7.0
CVE-2026-33672	medium	—	picomatch	4.0.3	1.7.0
CVE-2026-34043	medium	—	serialize-javascript	6.0.2	1.7.0

Showing 19 of 19