Skip to content

Add recommendation to update the runners - #2020

Merged
fdevans merged 1 commit into
4.0.xfrom
6.3-sec-runner-adv
Oct 23, 2026
Merged

fdevans merged 1 commit into
4.0.xfrom
6.3-sec-runner-adv

Conversation

@ronaveva

Copy link
Copy Markdown
Contributor

This pr add a recommendation for runner docker users regarding https://emudhra.we-have-a-problem.com/

@ronaveva ronaveva added this to the 6.3.0 milestone Oct 23, 2026
@ronaveva
ronaveva requested review from a team and fdevans and a balanced review from Copilot October 23, 2026 13:58
@fdevans
fdevans merged commit 327b360 into 4.0.x Oct 23, 2026
4 of 6 checks passed
@fdevans
fdevans deleted the 6.3-sec-runner-adv branch October 23, 2026 14:05

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The security-critical claim that Runner 6.3.0 images contain the CA remediation still needs confirmation from the image maintainers.

No open issues 🎉

What changed in this PR

Updates the eMudhra CA security advisory with remediation guidance for users running Runners in Docker or Kubernetes, including SaaS customers who manage their own Runners.

Changes:

  • Recommends pulling the Runner 6.3.0 image and recreating containers.
  • Clarifies that host-installed Runners use the host’s trust store.
  • Replaces the pending Runner verification note with explicit affected-image guidance.
File Description
docs/​history/​cves/​2026-10-emudhra-ca.md Adds Runner-specific impact and remediation guidance.

Review effort: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants