CVE-2023-4522Public exploitNetwork attack vector

Repository view disruption via LF-bearing directory names

Published Aug 30, 2023 · Updated May 26, 2026

Denial of service in GitLab before 16.2.0 allows remote authenticated users to disrupt repository views via LF-bearing directory names. GitLab accepts a line-feed character in a committed directory path, after which commit and diff rendering passes the malformed path into Gitaly lookups and view code that return object-not-found errors or dereference nil. A project account able to commit content is required; affected merge-request, comparison, commit, and repository views return HTTP 500 errors, while local Git access remains available.

CVSS severity4.3
Medium
EPSS probability1.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in GitLab before 16.2.0 allows remote authenticated users to disrupt repository views via LF-bearing directory names. GitLab accepts a line-feed character in a committed directory path, after which commit and diff rendering passes the malformed path into Gitaly lookups and view code that return object-not-found errors or dereference nil. A project account able to commit content is required; affected merge-request, comparison, commit, and repository views return HTTP 500 errors, while local Git access remains available.

The record

CVE
CVE-2023-4522
Published
Aug 30, 2023
Updated
May 26, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-1287, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 30, 2023CVE publishedPublication date reported by the CVE source.
  2. May 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <16.2.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=0 <16.2.0

Published CVSS scores

5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
4.3GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-1287Improper Validation of Specified Type of Input
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo