Secuno
ENNL
Book demo

CVE-2026-16301

Broken access control

8.5 HIGH
  1. Published13 Oct 2026

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with Developer role to execute CI/CD pipelines on protected branches without authorization due to improper authorization checks in the downstream pipeline creation service.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeChanged
ConfidentialityLow
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1095598.7
EdgeEver Desktop 1.6.26 through 1.112.0 contains a navigation allowlist bypass that…
CVE-2026-773669.9
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian…
CVE-2026-1039038.8
An incorrect authorization vulnerability in the WinBox authentication flow of MikroTik…
CVE-2026-1087468.8
Vearch 3.5.2 through 3.5.9 contains an incorrect authorization vulnerability in…
CVE-2026-816499.1
The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper…
CVE-2026-1085508.8
SkillHub before 0.2.22 contains an incorrect authorization vulnerability in…

Frequently asked

Is CVE-2026-16301 being actively exploited?

CVE-2026-16301 is not in the CISA KEV catalog.

How severe is CVE-2026-16301?

CVE-2026-16301 has a CVSS 3.1 base score of 8.5, rated high.

How do I fix CVE-2026-16301?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-16301 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.