ZDF
Sign inSign up

Vulnerabilities

Vulnerability · openSUSE-SU-2026:22126-1

Security update for gitoxide

Published Oct 19, 2026 · catalog updated Oct 20, 2026 · Security update for gitoxide

Open the advisory

Exploitation likelihood is not on this record for openSUSE-SU-2026:22126-1. A missing EPSS score is not a low risk. Compare Security update for gitoxide with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Security update for gitoxide).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
openSUSE:Leap 16.0 gitoxide

This update for gitoxide fixes the following issues: Changes in gitoxide: Update to version 0.60.0: * BREAKING: remove the full-screen progress mode: the --progress and --progress-keep-open flags and the prodash-render-tui feature are gone, line progress stays the only progress UI * Trace output is now independently configurable with a bounded -t/--trace counter, separate from verbose and progress rendering * Add gix worktree add (alias create) and worktree remove * Various security improvements and more consistent error handling across the plumbing crates - Refresh the vendored dependencies. The linked graph still carries MPL-2.0 only (uluru, option-ext); the License tag is unchanged. - Restore the explicit prodash feature dropped in the gix-utils 0.5.0 dep: migration, which broke workspace-wide cargo metadata --features as run by cargo-auditable. Update to version 0.59.0: * Ships gix-transport 0.60.0, which rejects NUL/LF in git-daemon connect requests: drops the backported fix for CVE-2026-91986 (boo#1281749), now fixed upstream * gix-transport-reject-control-bytes.patch * New gix editor command with Git-compatible selection * Raise the Rust floor to 1.88 (upstream MSRV, dua-core) - Refresh the vendored dependencies. The linked graph still carries MPL-2.0 only (uluru, option-ext); the License tag is unchanged. Update to 0.58.0: * gix tix is now the full gix-tix platform embedded in the plumbing command instead of a second parser and dispatcher, so standalone and plumbing invocations behave alike and amend and spill are reachable through gix tix * tix decorates commits checked out by other main or linked worktrees with light-blue name@ labels, keeps the marker for the checkout it was opened from, and watches linked HEAD and worktree membership so the decorations stay current * tix gained -w/--worktrees to add every resolved worktree HEAD to the traversal tips without weakening hidden-revision exclusions * gix tix no longer accepts --screen: the interactive history

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • openSUSE:Leap 16.0 gitoxide0 → 0.60.0-bp160.1.1

How to fix openSUSE-SU-2026:22126-1

  • Recommended remediation

    A patch or advisory reference is linked. Open the original publisher for availability by product version.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for openSUSE-SU-2026:22126-1. A missing EPSS score is not a low risk. Compare Security update for gitoxide with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 0.60.0-bp160.1.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 19, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    This update for gitoxide fixes the following issues: Changes in gitoxide: Update to version 0.60.0: * BREAKING: remove the full-screen progress mode: the --progress and --progress-keep-open flags and the prodash-render-tui feature are gone, line progress stays the only progress UI * Trace output is now independently configurable with a bounded -t/--trace counter, separate from verbose and progress

  2. Oct 20, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    gitoxide fixed in 0.60.0-bp160.1.1

  3. Oct 20, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    gitoxide fixed in 0.60.0-bp160.1.1

  4. Oct 20, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    This update for gitoxide fixes the following issues: Changes in gitoxide: Update to version 0.60.0: * BREAKING: remove the full-screen progress mode: the --progress and --progress-keep-open flags and the prodash-render-tui feature are gone, line progress stays the only progress UI * Trace output is now independently configurable with a bounded -t/--trace counter, separate from verbose and progress

Sources

References

Freshness

Last verified in this catalog Oct 20, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.