github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-07-15 21:16:40 -05:00
Code Issues 713 Packages Projects Releases 45 Wiki Activity

[PR #360] [MERGED] Upgrade cosign installer to v4.1.2 and pin cosign version #5388

New Issue
Closed
opened 2026-06-07 18:31:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-07 18:31:51 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/newt/pull/360
Author: @marcschaeferger
Created: 5/16/2026
Status: ✅ Merged
Merged: 5/16/2026
Merged by: @oschwartz10612

Base: main ← Head: github-action-cosign

📝 Commits (1)

  • 8736f89 fix(security): update cosign to v3.0.6 and installer to 4.1.2

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 .github/workflows/cicd.yml (+2 -2)

📄 Description

Description

Updates the Cosign installer workflow usage and explicitly pins the installed Cosign binary to v3.0.6.

Why

Cosign versions below 3.0.6 are affected by CVE-2026-39395. While this workflow was not explicitly pinned to an older vulnerable Cosign binary, the installed Cosign version was implicit and therefore less deterministic.

Changes

References

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/newt/pull/360 **Author:** [@marcschaeferger](https://github.com/marcschaeferger) **Created:** 5/16/2026 **Status:** ✅ Merged **Merged:** 5/16/2026 **Merged by:** [@oschwartz10612](https://github.com/oschwartz10612) **Base:** `main` ← **Head:** `github-action-cosign` --- ### 📝 Commits (1) - [`8736f89`](https://github.com/fosrl/newt/commit/8736f89291076ef66ce9477ef0ccfbea43001319) fix(security): update cosign to v3.0.6 and installer to 4.1.2 ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/cicd.yml` (+2 -2) </details> ### 📄 Description ## Description Updates the Cosign installer workflow usage and explicitly pins the installed Cosign binary to `v3.0.6`. ## Why Cosign versions below `3.0.6` are affected by CVE-2026-39395. While this workflow was not explicitly pinned to an older vulnerable Cosign binary, the installed Cosign version was implicit and therefore less deterministic. ## Changes - Updates `sigstore/cosign-installer` to `v4.1.2` https://github.com/sigstore/cosign-installer/releases/tag/v4.1.2 - Adds an explicit `cosign-release: v3.0.6` - Keeps the workflow behavior unchanged apart from using the fixed Cosign version ## References - CVE: https://www.suse.com/security/cve/CVE-2026-39395.html - Cosign installer usage: https://github.com/sigstore/cosign-installer#usage --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-07 18:31:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
dependencies
docker
enhancement
go
good first issue
help wanted
Improvement
needs investigating
pull-request
Mirrored from GitHub Pull Request
 stale
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#5388
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?