Security Deep Dive
daytona
Security posture and CVE patch evidence from tracked releases.
1 high-severity dependency CVE affects v0.184.0.
Review the dependency vulnerabilities below.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v0.184.0 | 2026-06-03 | — | — | — | — | — |
Latest
|
| v0.183.0 | 2026-05-29 | — | — | — | — | — |
—
|
| v0.182.0 | 2026-05-26 | — | — | — | — | — |
—
|
| v0.181.0 | 2026-05-25 | — | — | — | — | — |
—
|
| v0.180.0 | 2026-05-24 | — | — | — | — | — |
—
|
| v0.179.0 | 2026-05-21 | — | — | — | — | — |
—
|
| v0.178.0 | 2026-05-20 | — | — | — | — | — |
—
|
| v0.177.0 | 2026-05-15 | — | — | — | — | — |
—
|
| v0.176.0 | 2026-05-14 | — | — | — | — | — |
—
|
| v0.175.0 | 2026-05-12 | — | — | — | — | — |
—
|
| v0.174.0 | 2026-05-11 | — | — | — | — | — |
Patches
CVE-2026-42208
|
| v0.173.0 | 2026-05-06 | 1 | — | — | — | KEV 1 |
—
|
| v0.172.0 | 2026-05-05 | 1 | — | — | — | KEV 1 |
—
|
| v0.171.0 | 2026-04-30 | 1 | — | — | — | KEV 1 |
—
|
| v0.170.0 | 2026-04-27 | 1 | — | — | — | KEV 1 |
—
|
| v0.169.0 | 2026-04-23 | 1 | — | — | — | KEV 1 |
—
|
| v0.168.0 | 2026-04-21 | 1 | — | — | — | KEV 1 |
—
|
| v0.167.0 | 2026-04-16 | 1 | — | — | — | KEV 1 |
—
|
| v0.166.0 | 2026-04-15 | 1 | — | — | — | KEV 1 |
—
|
| v0.165.0 | 2026-04-14 | 1 | — | — | — | KEV 1 |
—
|
Trust Signals — 3 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.25 / 0.5
Max EPSS 0.569
freshness
1.00 / 1.0
Up to date
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.00 / 2.5
No open 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.0
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
1.5
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/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
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-2026-42208 | CRITICAL | 98%ile | — | v0.174.0 | — | — | 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
1
Medium
2
Low
0
Unknown
3
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-4867 | high | — | path-to-regexp | 0.1.12 | v0.174.0 |
| CVE-2026-41493 | medium | — | yard | 0.9.38 | v0.174.0 |
| GHSA-67mh-4wv8-2f99 | medium | — | esbuild | 0.21.5 | v0.174.0 |
| CVE-2026-33812 | unknown | — | golang.org/x/image | v0.38.0 | v0.174.0 |
| CVE-2026-33813 | unknown | — | golang.org/x/image | v0.38.0 | v0.174.0 |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | v0.174.0 |
Showing 6 of 230