dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45261

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GitButler is a modern Git-based version control interface for AI-powered workflows. Prior to 0.19.7, a emote code execution vulnerability exists in the Tauri-based GitButler desktop application. An attacker can inject a malicious link in a pull request body, which if clicked by the user allows for arbitrary script execution in the Tauri webview. Users that have not enabled forge integration are not at risk. This vulnerability is fixed in 0.19.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote code execution vulnerability exists in GitButler versions prior to 0.19.7 where an attacker can inject a malicious link into a pull request body. When a user with forge integration enabled clicks this link, arbitrary script execution occurs in the Tauri webview context, allowing the attacker to run commands on the victim's machine.

MitigationUpgrade to GitButler version 0.19.7 or later. Users without forge integration enabled are not vulnerable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitButler version
    Locate the installed GitButler application and retrieve its version number (typically found in the application UI, about section, or installed package metadata)
    Affected if Version is lower than 0.19.7 (any version prior to this release is affected)
  2. Verify forge integration status
    Inspect GitButler configuration settings to determine whether the forge integration feature is enabled
    Affected if Forge integration is currently enabled - this is required for the vulnerability to be exploitable
  3. Confirm Tauri webview context usage
    Verify that GitButler is running in a Tauri-based desktop environment (the vulnerability specifically targets the Tauri webview context)
    Affected if GitButler is running as a Tauri desktop application - this is the vulnerable runtime context

You are affected if your GitButler version is below 0.19.7 AND forge integration is enabled, allowing malicious PR links to execute arbitrary script in the Tauri webview.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to GitButler version 0.19.7 or later. Users without forge integration enabled are not vulnerable.

Recommended fix High confidence

0.19.7

  1. Verify current GitButler version by checking About or settings
  2. Ensure forge integration is enabled (check Settings > Integrations > Forge)
  3. Download GitButler version 0.19.7 from the official GitButler releases page or update through the application
  4. Update GitButler to version 0.19.7
  5. Restart the application after update
  6. Verify the update was successful by checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data