CVE-2026-105777

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-22) is not newer than that change (2026-10-30), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-107673 (ENISA EUVD) · GHSA-3w94-rpmr-77jr (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above (from the CVE record's solution, GitLab Inc.) — apply it.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6.5 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have retrieved sensitive internal server credentials due to improper filtering of internal response headers.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

October 21, 2026

Last Modified

October 30, 2026

Advisory Details (1)

Auto-updated Oct 22, 2026
Fix named in the CVE record's solution (GitLab Inc.).
Web page

GitLab Critical Patch Release: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/

Vendor Advisories for CVE-2026-105777(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 22× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-30 18:27 UTCGHSA enrichmentGHSA-3w94-rpmr-77jr · GitHub CVSS 4.3
  3. 2026-10-30 17:21 UTCEG score recompute
  4. 2026-10-30 17:21 UTCGHSA enrichmentGHSA-3w94-rpmr-77jr · GitHub CVSS 4.3
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  9. 2026-10-27 14:29 UTCEG score recompute▲ 2.20
  10. 2026-10-27 14:29 UTCGHSA enrichmentGHSA-3w94-rpmr-77jr · GitHub CVSS 4.3
  11. 2026-10-27 14:25 UTCNVD updateCVSS v3 → 6.5
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  13. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  14. 2026-10-25 14:55 UTCEG score recompute
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  18. 2026-10-22 16:28 UTCEG score recompute
  19. 2026-10-22 16:28 UTCGHSA enrichmentGHSA-3w94-rpmr-77jr · GitHub CVSS 4.3
  20. 2026-10-22 01:27 UTCEG score recompute
  21. 2026-10-21 23:45 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  22. 2026-10-21 23:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-105777?
CVE-2026-105777 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6.5 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have retrieved sensitive internal server credentials due to improper filtering of internal…
When was the CVE record for CVE-2026-105777 published?
The CVE record for CVE-2026-105777 was published on October 21, 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-105777 actively exploited?
CVE-2026-105777 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105777?
CVE-2026-105777 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-105777?
The CVE record's solution for CVE-2026-105777, written by its CNA GitLab Inc., names the fix: "Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above." The vendor advisories EchelonGraph has for CVE-2026-105777 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105777?

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

Book a Demo →Browse All CVEs