GitLabApplication
CVE-2019-15726
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in GitLab Community and Enterprise Edition through 12.2.1. Embedded images and media files in markdown could be pointed to an arbitrary server, which would reveal the IP address of clients requesting the file from that server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitLab allows embedding images and media files in markdown. When users view markdown content containing references to external servers, their client IP addresses are disclosed to those arbitrary third-party servers when the browser requests the external resources. This is an information disclosure vulnerability affecting all users viewing crafted markdown content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
< 12.0.8>= 12.1.0, < 12.1.8>= 12.2.0, < 12.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun `cat /opt/gitlab/version` or `gitlab-rake gitlab:env:info` to retrieve the exact GitLab version numberAffected if The version falls into any of these ranges: < 12.0.8, >= 12.1.0 and < 12.1.8, or >= 12.2.0 and < 12.2.3
-
Determine if markdown rendering is in useCheck if users can create or view markdown content (issues, merge requests, comments, wiki pages) in the GitLab instanceAffected if Markdown rendering is enabled and users can view content created by others
-
Verify external resource requests are not blockedInspect network configuration, proxy settings, or GitLab external request settings at the infrastructure levelAffected if The version is in the affected ranges AND the instance processes markdown content visible to users
A user is affected if their GitLab version is less than 12.0.8, between 12.1.0 and 12.1.7 inclusive, or between 12.2.0 and 12.2.2 inclusive, and users can view markdown containing external image or media references.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data12.0.812.1.812.2.3
Upgrade GitLab to version 12.2.1 or later. Alternatively, implement network-level controls to proxy or block external resource requests from client browsers.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data