Secuno
ENNL
Book demo

CVE-2026-79708

8.5 HIGHEPSS 0.34%
  1. Published16 Sept 2026

Description

GitLab has remediated an issue in GitLab EE affecting all versions from 19.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions could have allowed an authenticated user with developer permissions to execute a policy test pipeline on projects within their group and access protected CI/CD variables restricted to higher-privileged roles, due to insufficient scope validation.

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-275528.1
A low-privileged remote attacker can exploit improper authorization in the…
CVE-2026-917358.3
Incorrect authorization in WebUI in Google Chrome prior to 153.0.8010.47 allowed a…
CVE-2026-634438.3
Coder allows organizations to provision remote development environments via Terraform.…
CVE-2026-540768.1
ArcadeDB is a Multi-Model DBMS. Prior to 26.6.1, the fix for CVE-2026-44221 added an…
CVE-2026-886168.8
An issue in RuoYi-Vue-Plus 6.0.0 allows a remote attacker to execute arbitrary code via…
CVE-2026-161408.8
OpenBMC's IPMI implementation, phosphor-net-ipmid, is vulnerable to a logic flaw where…

Frequently asked

Is CVE-2026-79708 being actively exploited?

CVE-2026-79708 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.34%.

How severe is CVE-2026-79708?

CVE-2026-79708 has a CVSS 3.1 base score of 8.5, rated high. EPSS estimates a 0.34% probability of exploitation.

How do I fix CVE-2026-79708?

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-79708 against the real software inventory on every managed device, every day. 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

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