Git ChangelogApplication · Jenkins
CVE-2018-1000426
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 · uneditedA cross-site scripting vulnerability exists in Jenkins Git Changelog Plugin 2.6 and earlier in GitChangelogSummaryDecorator/summary.jelly, GitChangelogLeftsideBuildDecorator/badge.jelly, GitLogJiraFilterPostPublisher/config.jelly, GitLogBasicChangelogPostPublisher/config.jelly that allows attackers able to control the Git history parsed by the plugin to have Jenkins render arbitrary HTML on some pages.
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 confidenceThe Jenkins Git Changelog Plugin versions 2.6 and earlier fails to sanitize Git history data (commit messages, author info) before rendering it in Jelly template files. An attacker who can control Git history (by pushing malicious commit messages) can inject arbitrary HTML/JavaScript that executes in the browsers of other Jenkins users viewing the changelog.
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
Git ChangelogApplication
<= 2.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify Git Changelog Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Git Changelog', or list files in $JENKINS_HOME/plugins/ directory looking for git-changelog.jpi or git-changelog.hpiAffected if The plugin file exists in the plugins directory or is listed in the Installed tab
-
Determine the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, locate the Git Changelog plugin and note the version number displayedAffected if The version is 2.6 or earlier (e.g., 2.6, 2.5, 2.4, etc.)
-
Identify jobs using the Git Changelog pluginReview job configurations in $JENKINS_HOME/jobs/ or through the Jenkins UI to find builds that invoke the Git Changelog plugin, typically by searching for 'gitChangelog' or 'changelog' in job XML config filesAffected if Any job is configured to use the Git Changelog plugin and generate changelogs from Git history
-
Confirm the vulnerable rendering path is accessibleVerify that users can access job build pages where the changelog is displayed. Check if any builds have already generated changelogs from Git repositoriesAffected if Jenkins users can view Git changelogs generated by the plugin in build console output or dedicated changelog views
Your environment is affected if the Git Changelog Plugin is installed at version 2.6 or earlier AND at least one job uses the plugin to render Git history to users.
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 dataUpdate the Git Changelog Plugin to a version later than 2.6 that includes proper output encoding. Until patched, restrict repository access to trusted contributors and review commits before integration.
Fix this in Git Changelog
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000426 — 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-2018-1000426 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