CVE-2026-85706
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19... Source description excerpt; complete tracked detail loads below.
Source reported · Source: CVE record · Source last published: · Source last updated: · Tracker data as of:
What is affected
ReportedGitLab; Community Edition and Enterprise Edition. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: CVE record · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedAct · 460.5
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
ReportedActive exploitation · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog
Source reported · Active since: · CISA KEV added: · VulnCheck KEV added: · ENISA added: · Source last updated: · Tracker data as of:
What to do
ReportedApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Source remediation ↗Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:
Evidence detail
Loading the full tracker evidence record…