CVE-2026-69261

HIGHPre-NVD 7.67.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source

Also known asEUVD-2026-130402 (ENISA EUVD) · GHSA-x7xj-4j4f-88xr (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential values. Authorization headers are never forwarded to inappropriate hosts and are not the affected secret in this vulnerability. This issue is fixed in version 3.8.1.

CVSS
7.6
EG Score
7.6HIGHlow confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Advisory Details (6)

Auto-updated Nov 19, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v3.8.1

Patch available: git-lfs/git-lfs v3.8.1

https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
GitHub commit

commit d65324a7d510 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit d65324a7d510 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/d65324a7d5104c7a5dcb8c4959933695c8bc10fa
GitHub commit

commit 537203a1fa08 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit 537203a1fa08 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/537203a1fa08fdde4c16288fb039174ff0e692bb
GitHub commit

commit 256d371024e6 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit 256d371024e6 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/256d371024e6d2cf19efe675d8b9ad089785d0a1
GitHub commit

commit 12c92e05b343 (git-lfs/git-lfs)

Fix landed in git-lfs/git-lfs commit 12c92e05b343 — awaiting tagged release

https://github.com/git-lfs/git-lfs/commit/12c92e05b3433494d4b8695943e7e230744d77d9
GitHub advisoryMentions a patch (unverified)

Git LFS may leak HTTP headers after redirections · Advisory · git-lfs/git-lfs · GitHub

Affected: v3.8.1. All users should upgrade to v3.8.1.

https://github.com/git-lfs/git-lfs/security/advisories/GHSA-x7xj-4j4f-88xr

Vendor Advisories for CVE-2026-69261(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/git-lfs/git-lfs—ghsa
gogithub.com/git-lfs/git-lfs/v3 @ 3.8.1 (fixes >= 3.0.0, < 3.8.1)—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 23:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-11-20 15:54 UTCGHSA enrichmentGHSA-x7xj-4j4f-88xr · GitHub severity HIGH
  5. 2026-11-20 01:38 UTCEchelonGraph re-scored
  6. 2026-11-19 18:03 UTCENISA EUVD ID recordedEUVD-2026-130402 · Source: ENISA EUVD
  7. 2026-11-19 17:28 UTCEchelonGraph re-scored
  8. 2026-11-19 16:59 UTCEchelonGraph re-scoredFirst assessed: 7.6 HIGH
  9. 2026-11-19 16:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69261?
CVE-2026-69261 is a high-severity vulnerability; its CVE record was published on November 19, 2026. Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential…
When was the CVE record for CVE-2026-69261 published?
The CVE record for CVE-2026-69261 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-69261 actively exploited?
CVE-2026-69261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69261?
CVE-2026-69261 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-69261?
A fix for CVE-2026-69261 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69261 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69261

Explore →

Is Your Infrastructure Affected by CVE-2026-69261?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.