CVE-2026-121614

Read full description

Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands. An attacker who can modify a host repository's Git configuration, for example through a direct-mode sandbox with the repository mounted read-write, can configure core.fsmonitor or another Git setting that invokes an external program. Git can execute the program during a later clone-mode fetch or, starting in version 0.39.0, an sbx kit push initiated by the user. The program runs on the host with the invoking user's permissions, outside the sandbox's microVM isolation. The read-only host repository mount provided to a clone-mode sandbox does not itself allow that sandbox to modify the host repository's Git configuration. The issue is fixed in version 0.50.0.

CVSS 7.1 (HIGH)

Attention and evidence

HYPE SCORE

0.0/10

REALITY · THREAT PRIORITY

2.5/10

General review priority; not probability

Evidence confidence: Insufficient evidence

Why this priority?

Technical severity: CVSS 7.1: +2.48
Fresh EPSS: 0.13%: +0.00

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 1 documents and public datasets.

Hype components

Headline sample (25%)

0/100

Press, 30 days (60%)

0/100

Grounded branding (15%)

0/100

HYPE TOTAL0/100

Sources and documents

Latest Vulnerabilities

Technical advisory · 03 Nov 2026, 22:19 · CVE-2026-121614 - Docker Sandboxes host Git executes repository-controlled programs

Score evolution

● Hype ● Reality

━ Hype Score (Perceived) ━ Reality threat priority. Definition changes are not new attacks.

Public exploit evidence

Public exploit entries / repo candidates

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 3 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence: Insufficient evidence
Priority basis: Exploitation in attacks unconfirmed; CVSS 7.1; EPSS 0.1%
Attention, last 30 days: 0 distinct story titles; 0 press documents; 0 publisher domains.
Technical potential: local access, no prior privileges, active user interaction, additional attack conditions.
Observed activity: No exploitation observation is recorded.
Known scale: Not quantified.
Evidence confidence basis: Insufficient evidence

Score evaluated: 2026-11-05 13:59:56.876805+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z

Source event timeline

Published

03 Nov 2026, 21:54

Score calculated

05 Nov 2026, 13:59