sbomify Insights

Search by CVE or GitHub advisory id, package name or title.

CVE-2025-1754 Missing Authentication for Critical Function in GitLab

Medium 5.3 Published Updated

Unauthenticated attackers can upload arbitrary files to public GitLab projects via API, enabling resource abuse and unauthorized content storage.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-1754?

CVE-2025-1754 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An issue has been discovered in GitLab CE/EE affecting all versions from 17.2 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed unauthenticated attackers to upload arbitrary files to public projects by sending crafted API requests, potentially leading to resource abuse and unauthorized content storage.

Weakness: CWE-306

Which versions are affected by CVE-2025-1754?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 17.2.018.0.1

Products include Gitlab Gitlab.

How do I fix CVE-2025-1754?

Upgrade gitlab to 18.0.1 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2025-1754 being exploited?

There is no known exploitation of CVE-2025-1754 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2025-1754, GHSA-82v9-h229-pq5f, UBUNTU-CVE-2025-1754.

Is CVE-2025-1754 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free