CVE Intelligence
Low File handling exploit reference

CVE-2026-14288 — Use of Incorrectly-Resolved Name or Reference in GitLab

GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that under certain conditions could have allowed an authenticated to bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization.

Published Oct 21, 2026 · Updated Oct 22, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: GitLab

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Gitlab
Gitlab
CVSS base
3.1
Low · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Gitlab Gitlab).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Gitlab Gitlab ≥ 17.4 and < 19.3.6≥ 19.4 and < 19.4.3≥ 19.5 and < 19.5.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
3.1 CVSS 3.1 Low 1.6 1.4 cve@gitlab.com via NIST National Vulnerability Database
3.1 CVSS 3.1 Low — — GitLab via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N (score shown at the top: cve@gitlab.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-706 · Use of Incorrectly-Resolved Name or Reference

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 21, 2026 · GitLab
  • Record published
    Oct 21, 2026
  • CVSS changed · 3.1
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

3 on the record

Elsewhere on this site

Gitlab
every CVE for this vendor
File handling
same class
CWE-706
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-12664 Incorrect Authorization in GitLab 21h
  • CVE-2026-16255 Incorrect Authorization in GitLab 21h
  • CVE-2026-15723 Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in GitLab 21h
  • CVE-2026-13319 Authorization Bypass Through User-Controlled Key in GitLab 21h
  • CVE-2026-112378 Use of Less Trusted Source in GitLab 21h
  • CVE-2026-105777 Insertion of Sensitive Information Into Sent Data in GitLab 21h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-14288 is "Use of Incorrectly-Resolved Name or Reference in GitLab", rated Low. It affects Gitlab (Gitlab); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.