chore(deps): claircore SSRF advisory (2 medium alerts) — indirect, no patched version yet

[devantler]

🤖 Generated by the Daily AI Engineer

Evidence

Dependabot alerts #165/#166 (medium): claircore <= 1.5.52 — "Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints" (SSRF in claircore's manifest handling). ksail pins github.com/quay/claircore v1.5.35 indirect via the scan toolchain; first_patched_version is null, so no bump exists today and dependabot cannot propose one.

Reachability assessment

ksail never runs a claircore service — the vulnerable surface is claircore's own manifest-ingestion endpoints, not the library paths a scanner consumer exercises. Risk to ksail users is accordingly assessed low; this issue exists so the alert is owned, not ignored.

Acceptance criteria

• When upstream publishes a patched claircore, bump it (dependabot will propose it; drive that PR to green/merge) and confirm alerts Add ksail formula to Homebrew core #165/Update publish.yaml #166 auto-resolve.
• If no patch ships within ~a quarter, re-assess: dismiss the alerts with the reachability rationale (recorded here) or pin an upstream fix.

Blocked on: upstream patched release (none as of 2026-07-17).

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Track Claircore manifest URI SSRF exposure #6008

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!