CVE-2022-2826
First published: Fri Oct 28 2022(Updated: )
An issue has been discovered in GitLab affecting all versions starting from 10.0 before 12.9.8, all versions starting from 12.10 before 12.10.7, all versions starting from 13.0 before 13.0.1. TODO
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.0.0<12.9.8 | |
| GitLab | >=12.10.0<12.10.7 | |
| GitLab | =13.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-2826?
CVE-2022-2826 is classified as a critical vulnerability affecting specific versions of GitLab.
How do I fix CVE-2022-2826?
To remediate CVE-2022-2826, upgrade GitLab to the latest version that includes the patch for the vulnerability.
Which versions of GitLab are affected by CVE-2022-2826?
CVE-2022-2826 affects GitLab versions starting from 10.0 up to 12.9.8, 12.10 up to 12.10.7, and exactly version 13.0.0.
What might happen if I don't address CVE-2022-2826?
Failing to address CVE-2022-2826 can lead to unauthorized access and exploitation of the affected GitLab instance.
Is CVE-2022-2826 part of a larger issue in GitLab?
CVE-2022-2826 is one of several vulnerabilities that have been identified in GitLab, emphasizing the need for regular updates and security assessments.
- agent/type
- agent/references
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/10.0.0
- version/gitlab/12.10.0
- version/gitlab/13.0.0