CVE-2026-40034VulnerabilityPublished 30 Jun 2026Updated 10 Nov 2026

SUSE · Security update for stgit

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-40034· High 7.3

Not known to be exploited · CVSS 7.3 High · fixed in SUSE package updates : patch SUSE gitoxide soon.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 4.0 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	7.3
CNA (VulnCheck)	CVSS 3.1	7.8

Patch: Available – fixed in 0.5.21, 0.29.0, 0.84.0

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 26 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulnCheck
8 Apr 202613:36 UTC, 48 days before disclosure
CVE published
on cve.org
26 May 202614:08 UTC, t = 0
CISA SSVC assessment
proof of concept public
26 May 202615:00 UTC, 52 minutes after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitoxide to 0.5.21; gix-submodule to 0.29.0; gix to 0.84.0.

Affected software

Product	Affected	Fixed in
gitoxidegitoxide	Affected <0.5.21	Fixed in 0.5.21
gitoxidegix-submodule	Affected <0.29.0	Fixed in 0.29.0
gitoxidegix	Affected <0.84.0	Fixed in 0.84.0
crates.iogitoxide`pkg:cargo/gitoxide`Other threats	Affected <0.5.21	Fixed in 0.5.21
crates.iogix-submodule`pkg:cargo/gix-submodule`Other threats	Affected <0.29.0	Fixed in 0.29.0
crates.iogix`pkg:cargo/gix`Other threats	Affected <0.84.0	Fixed in 0.84.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for stgit fixes the following issues: Changes in stgit: - Update to version 2.6.0: * chore: update changelog for 2.6.0 * fix(import): respect --name verbatim, ignoring stgit.namelength * test(refresh): use test_when_finished for status.renames cleanup * expect over unwrap for test * bugfix: issue #615, add Copied variant to Status enum and move panic to a copied status, add integration test * docs: Update copyright year * chore: update gix to 0.83 (CVE-2026-40034, bsc#1266429) * chore: update compatible transitive dependencies * chore: update winnow to 1.0.3 * chore: update jiff to 0.2.24 * ci: drop dead CARGO_TARGET_*_STRIP env vars from package build * ci: soft-pin cargo-deb to ^3.0 * ci: bump cargo-generate-rpm pin to ^0.20.0 * ci: bump GitHub Actions to Node 24 runtimes * chore: update winnow to 1.0.1 * chore: update clap to 4.6.1 * chore: update gix to 0.81 * chore: bump MSRV to 1.85 * chore: update transitive deps * chore: update winnow to 0.7.15 * chore: update thiserror to 2.0.18 * chore: update tempfile to 3.27.0 * chore: update tar to 0.4.45 * chore: update serde_json to 1.0.149 * chore: update jiff to 0.2.23 * chore: update indexmap to 2.14.0 * chore: update flate2 to 1.1.9 * chore: update ctrlc to 3.5.2 * chore: update clap to 4.5.61 * chore: update anyhow to 1.0.102 * chore: update anstyle to 1.0.14 - Update to version 2.5.5: * fix(squash): keep author when squashed commits have same author - Update to version 2.5.4: * chore: update changelog for 2.5.4 * chore: update transitive dependencies * chore: update clap to 4.5.43 * refactor: clippy fixes * fix: gix 0.73 breaking changes * chore: update gix to 0.73 * chore: update transitive dependencies * chore: update serde_json to 1.0.142 * chore: update winnow to 0.7.12 * chore: update clap to 4.5.42 * refactor: clippy lints * stgit.el: Use `with-eval-after-load' instead of a homemade version * stgit.el: Use `advice-add' instead of `defadvice' * stgit.el: Fix various checkdoc warnings * stgit.el: Support Emacs versions < 31 * feat(bash): complete patches from chosen branch * chore: update dependencies * refactor: repair clippy lints * chore: update clap to 4.5.40 * chore: update anstyle to 1.0.11 * chore: update winnow to 0.7.11 * chore: update anyhow to 1.0.98 * chore: update jiff to 0.2.15 * chore: update tempfile to 3.20.0 * chore: update curl to 0.4.48 * chore: update flate2 to 1.1.2 * chore: update ctrlc to 3.4.7 * chore(deps): bump winnow from 0.7.6 to 0.7.10 * chore(deps): bump clap from 4.5.36 to 4.5.39 * docs: Update copyright year * chore: update transitive dependencies * chore: update tempfile to 3.19.1 * chore: update jiff to 0.2.6 * chore: update winnow to 0.7.6 * chore: update gix to 0.71 * chore: update indexmap to 2.9.0 * chore: update is-terminal to 0.4.16 * chore: update ctrlc to 3.4.6 * chore: update bstr to 1.12.0 * chore: update clap to 4.5.36 * chore: update flate2 to 1.1.1 * chore: update serde to 1.0.219 * chore: update serde_json to 1.0.140 * chore: update thiserror to 2.0.12 * chore: update anyhow to 1.0.97 * refactor: repair clippy lint * stgit.el: Move 'stgit-patch-status-face-alist' before first use * stgit.el: Silence warnings of missing vc variables * stgit.el: Replace ad-hoc `make-local-variable' with `defvar-local' * stgit.el: Use defvar-local instead of make-local-variable * stgit.el: Enable lexical-binding * stgit.el: Allow empty descriptions * stgit.el: Add "--no-color" flag to 'git log' and 'git show' * stgit.el: Pass patch into `stgit-process-files' * chore: update changelog for 2.5.3 * chore: update dependencies * refactor(stgit.el): use space-based indentation consistently * refactor: repair clippy lint * chore(deps): bump tempfile from 3.16.0 to 3.17.0 * chore(deps): bump jiff from 0.2.0 to 0.2.1 * build: statically linked packages for riscv64 * chore: update changelog for 2.5.2 * chore: update jiff to 0.2.0 * chore: update winnow to 0.7.2 * fix: partial_ref_name * chore: resolve winnow deprecations * chore: update dependencies * ci: disable test for windows build * chore(deps): bump jiff from 0.1.24 to 0.1.29 * chore(deps): bump serde_json from 1.0.135 to 1.0.138 * chore(deps): bump is-terminal from 0.4.13 to 0.4.15 * chore(deps): bump indexmap from 2.7.0 to 2.7.1 * chore(deps): bump clap from 4.5.26 to 4.5.28 * stgit.el: Fix various compile warnings * stgit.el: Replace depercated cl function calls with new style * stgit.el: Fix some checkdoc warnings * stgit.el: Fix emacs pre-pending "Summary: " to log-edit buffers * chore: update changelog for 2.5.1 * chore: update release checklist * ci: use ubuntu-24.04 image * fix: assure branch creation respects fetch-specs of remotes. (#522) * chore: update to latest `gix` for improved API (#522) * chore: update transitive dep

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

Technical details

References

Community reviews

Related threats