CVE-2026-3854

Published Mar 10, 2026

Last updated 6 months ago

Overview

Description
An improper neutralization of special elements vulnerability was identified in GitHub Enterprise Server that allowed an attacker with push access to a repository to achieve remote code execution on the instance. During a git push operation, user-supplied push option values were not properly sanitized before being included in internal service headers. Because the internal header format used a delimiter character that could also appear in user input, an attacker could inject additional metadata fields through crafted push option values. This vulnerability was reported via the GitHub Bug Bounty program and has been fixed in GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7 and 3.19.4.
Source
product-cna@github.com
NVD status
Modified
Products
enterprise_server

Risk scores

CVSS 4.0

Type
Secondary
Base score
8.7
Impact score
-
Exploitability score
-
Vector string
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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
Severity
HIGH

CVSS 3.1

Type
Primary
Base score
8.8
Impact score
5.9
Exploitability score
2.8
Vector string
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

product-cna@github.com
CWE-77

Social media

Hype score
Not currently trending
  1. Bug bounty news: GitHub disclosed a critical RCE vulnerability in its Git push pipeline, tracked as CVE-2026-3854. The vulnerability was reported through GitHub’s Bug Bounty Program by Wiz researchers. GitHub says it validated the report within 40 minutes and deployed a fix to

    @NitinGavhane_

    17 Sept 2026

    465 Impressions

    1 Retweet

    9 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  2. CVE-2026-3854. One Push to Own Them All: CVE-2026-3854 and the Injection Flaw Inside GitHub's git Pipeline

    @lyrie_ai

    16 Jun 2026

    31 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  3. The Push That Compromised Millions: GitHub CVE-2026-3854 (RCE via Git Push). Wiz researchers discovered CVE-2026-3854, a critical RCE vulnerability in GitHub affecting both https://t.co/egGEC9VaCp and GitHub Enterprise Server GHES.

    @lyrie_ai

    6 Jun 2026

    87 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  4. 2026 POC REPORT CVE-2026-41089 WinNetlogon RCE PoC: https://t.co/22dqVfDXKx CVE-2026-31431 K8s Escape PoC: https://t.co/hecVZZEAFH CVE-2026-3854 GitHub RCE PoC: https://t.co/U0pmzvzvs6 CVE-2026-42897 Exchange XSS src: https://t.co/GKt5HlN8Gf

    @AlikBurton

    5 Jun 2026

    1 Impression

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  5. GitHub RCE Vulnerability: CVE-2026-3854 Breakdown https://t.co/ExPgTD3RDi

    @Komodosec

    28 May 2026

    48 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. One Git Push to Own Them All: CVE-2026-3854 Exposes the Developer Toolchain as the New Kill Chain. GitHub patched CVE-2026-3854, a critical command injection flaw in its git infrastructure babeld, on March 4, 2026—but didn't disclose it until April 28.

    @lyrie_ai

    28 May 2026

    37 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  7. One Git Push Away: CVE-2026-3854 Exposes Millions of GitHub Repos to RCE. One Git Push Away: How CVE-2026-3854 Turned GitHub's Backend Into an Open Door

    @lyrie_ai

    25 May 2026

    49 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  8. Wiz used AI to find CVE-2026-3854. Think about that for a second. AI audited GitHub's pipeline and found a critical trust propagation failure. The same week, my VATA batteries confirmed AI pipelines have the same failure. The tool that found the bug has the bug. CVE-2026-3854:

    @Lhmisme

    20 May 2026

    86 Impressions

    1 Retweet

    2 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Top 5 Trending CVEs: 1 - CVE-2020-17103 2 - CVE-2026-8507 3 - CVE-2026-3854 4 - CVE-2026-46333 5 - CVE-2025-54957 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    20 May 2026

    382 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    1 Quote

  10. Top 5 Trending CVEs: 1 - CVE-2026-34078 2 - CVE-2026-31431 3 - CVE-2024-27867 4 - CVE-2026-3854 5 - CVE-2026-34263 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    13 May 2026

    129 Impressions

    0 Retweets

    1 Like

    1 Bookmark

    0 Replies

    0 Quotes

Configurations