Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-71556: go-git: Worktree operations may follow symlinks

CVE-2026-71556 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
7.1 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L · base score 7.1, scored by GitHub_MAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: required. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: low.
Weakness
  • CWE-59: Improper Link Resolution Before File Access ('Link Following')
EPSS
0.36% chance of exploitation in the next 30 days (30th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: 5.19.2, 6.0.0-alpha, flightctl-0:1.1.4-1.el10em, flightctl-0:1.1.4-1.el9em, flightctl-0:1.2.1-1.el10, flightctl-0:1.2.1-1.el9 and 44 more in the advisory
Vendor advisories
2 from Red Hat, Veeam
Assigned by
GitHub_M (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-71556; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

go-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, worktree operations (including checkout, status, and add) resolve symbolic links inside the working tree without confining resolution to the worktree boundary, so a maliciously crafted repository containing a symlink can cause go-git to read from or write to files outside the intended working directory when the repository is cloned and its worktree operations are used. Versions 5.19.2 and 6.0.0-alpha.5.

Text from the CVE.org record (GitHub_M).

How do I fix CVE-2026-71556?

Upgrade to a fixed release named by the vendor:

  • Red Hat: 5.19.2, 6.0.0-alpha, flightctl-0:1.1.4-1.el10em, flightctl-0:1.1.4-1.el9em, flightctl-0:1.2.1-1.el10, flightctl-0:1.2.1-1.el9
  • To reduce the risk of exploitation, do not clone or run worktree operations (checkout, status, add) on Git repositories originating from untrusted or attacker-controllable sources using an affected version of go-git. The issue is resolved by updating to go-git 5.19.2 or 6.0.0-alpha.5 (or later). (Red Hat)

Vendor advisories for CVE-2026-71556

Red Hat

1 advisory
  • Advisory severityHigh7.1

    High [CVE-2026-71556] Arbitrary file read/write via symbolic link resolution

    CVE-2026-71556Source published Source updated

    go-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, worktree operations (including checkout, status, and add) resolve symbolic links inside the working tree without confining resolution to the worktree boundary, so a maliciously crafted repository containing a symlink can cause go-git to read from or write to files outside the intended working directory when the repository is cloned and its worktree operations are used. This could result in information disclosure or arbitrary file modification. Exploitation requires the application to clone an attacker-controlled repository and then perform worktree operations against it; applications that only process trusted repositories are not exposed. Red Hat rates the impact of this flaw as…

    Affected products in this advisory
    • RHEM 1.1 for RHEL 10
    • RHEM 1.1 for RHEL 9
    • RHEM 1.2 for RHEL 10
    • RHEM 1.2 for RHEL 9

    46 more entries in the full advisory.

    Source-reported affected versions
    • < 5.19.2
    • < 6.0.0-alpha
    • 6.0.0
    Source-reported fixed versions
    • 5.19.2
    • 6.0.0-alpha
    • flightctl-0:1.1.4-1.el10em
    • flightctl-0:1.1.4-1.el9em

    46 more entries in the full advisory.

    Mitigation guidance
    • To reduce the risk of exploitation, do not clone or run worktree operations (checkout, status, add) on Git repositories originating from untrusted or attacker-controllable sources using an affected version of go-git. The issue is resolved by updating to go-git 5.19.2 or 6.0.0-alpha.5 (or later).

Veeam

1 advisory
  • Advisory severityCritical

    Critical [CVE-2020-14040 +123] List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

    KB4825Source published

    This bulletin covers 124 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: Purpose This article aims to provide our customers' security and compliance teams with detailed information on security improvements. - Veeam Kasten for Kubernetes — Release Notes - Improved the protection of credentials used by block mode data mover operations and file recovery sessions. - Hardened the FileRecoverySession CR and file recovery pod with stricter input validation, restrictive mount options and a read-only SFTP service. - Passwords in proxy URLs are now masked in logs and the support bundle. - The multi-cluster proxy no longer forwards the caller's session and authentication credentials to secondary…

    Affected products in this advisory
    • Veeam Kasten for Kubernetes
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • 8.5.10
    • 8.5.5
    • 1.26.1
    • 8.5.3

    20 more entries in the full advisory.

    Mitigation guidance
    • List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Veeam Kasten for Kubernetes | 7 | 7.5 | 8 | 8.5 | 9 Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: 2026-11-16 Purpose This article describes all security-related fixes and improvements introduced in each release or update of Veeam Kasten for Kubernetes.
    • It is recommended to upgrade Veeam Kasten and to refresh the token by manually logging out.
    • Mitigation: Configure a bucket-level Default Object Lock retention so the object store stamps new objects at write time, or upgrade to Kasten 8.5.10.
    • Veeam Kasten for Kubernetes 8.5.5 Upgrade to Go 1.26.1 to address CVE-2026-25679 and CVE-2026-27142 Updated the UBI base image to address CVE-2026-4111 Veeam Kasten for Kubernetes 8.5.3 Upgrade to Go 1.25.7 to address CVE-2025-61732.

    4 more entries in the full advisory.

    Workarounds
    • Improved the protection of credentials used by block mode data mover operations and file recovery sessions.
    • Veeam Kasten for Kubernetes 8.0.14 Improved logging security for specific block mode datamover upload Pod invocations.

References

Timeline

  1. First vendor advisory listed by VulniPulse
  2. CVE record published
  3. CVE record last updated

All Red Hat advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat