CVE-2018-16976: Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access

Q: How do I fix CVE-2018-16976?

gitolite: upgrade to 3.6.9. Exact commands for each OS are on this page.

Q: Is CVE-2018-16976 being exploited?

CVE-2018-16976 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-16976 affect?

CVE-2018-16976 affects gitolite. Severity is high (CVSS 8.1). Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access to a Git repository that is in the process of being migrated until the full set of migration steps has been completed. This can al

This month

HIGH 8.1UPGRADE

CVE-2018-16976 is a high-severity flaw (CVSS 8.1) affecting gitolite. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access to a Git repository that is in the process of being migrated until the full set of migration steps has been completed. This can allow valid users to obtain unintended access.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-362
Published	2018-09-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: gitolite

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-09-12 22:29 UTCPublished CVE record published
2026-06-17 01:45 UTCUpdated Record last modified

gitolite gitolite UPGRADE

Affected: < 3.6.9

Fixed in: 3.6.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gitolite || rpm -q gitolite || gitolite --version

2. UPGRADE to 3.6.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitolite

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitolite

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-16976?

gitolite: upgrade to 3.6.9. Exact commands for each OS are on this page.

Is CVE-2018-16976 being exploited?

CVE-2018-16976 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-16976 affect?

CVE-2018-16976 affects gitolite. Severity is high (CVSS 8.1). Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access to a Git repository that is in the process of being migrated until the full set of migration steps has been completed. This can al

How urgent is CVE-2018-16976?

Priority 45/100. High severity

Software pages

Git vulnerabilities

Related CVEs

CVE-2018-20683 HIGH 8.1 UPGRADE commands/rsync in Gitolite before 3.6.11, if .gitolite.rc enables rsync, mishandles the rsync command line, wh
CVE-2013-7203 MEDIUM 5.5 UPGRADE gitolite before commit fa06a34 might allow local users to read arbitrary files in repositories via vectors rel
CVE-2013-4451 CRITICAL 9.8 UPGRADE gitolite commit fa06a34 through 3.5.3 might allow attackers to have unspecified impact via vectors involving w
CVE-2010-2447 CRITICAL 9.8 UPGRADE gitolite before 1.4.1 does not filter src/ or hooks/ from path names.

References

← Back to latest CVEs