How severe is CVE-2019-10416?

CVE-2019-10416 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10416?

CVE-2019-10416 affects the following packages: org.jenkins-ci.plugins:violation-comments-to-gitlab (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10416?

Update org.jenkins-ci.plugins:violation-comments-to-gitlab to 2.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10416 is resolved across your whole dependency graph.

How do I detect CVE-2019-10416 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:violation-comments-to-gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-10416 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-10416 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10416 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-10416?

CVE-2019-10416 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10416?

CVE-2019-10416 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-10416 published, and has it been updated?

CVE-2019-10416 was published on September 25, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2019-10416 — violation-comments-to-git…

MEDIUMFix: jenkinsci/violation-comments-to-gitlab-plugin@e8237a8

CVE-2019-10416 is a medium-severity (CVSS 6.5) CWE-522 vulnerability in org.jenkins-ci.plugins:violation-comments-to-gitlab. A fix is available for org.jenkins-ci.plugins:violation-comments-to-gitlab — see the affected versions and patch details below.

Violation Comments to GitLab Plugin has Insufficiently Protected Credentials

Also known asGHSA-3p8r-p4q5-mc44

Published

Sep 25, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:violation-comments-to-gitlab

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Violation Comments to GitLab Plugin stored API tokens unencrypted in job config.xml files and its global configuration file org.jenkinsci.plugins.jvctgl.ViolationsToGitLabGlobalConfiguration.xml on the Jenkins controller. These credentials could be viewed by users with Extended Read permission, or access to the Jenkins controller file system.

Violation Comments to GitLab Plugin now stores these credentials encrypted. Existing jobs need to have their configuration saved for existing plain text credentials to be overwritten.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:violation-comments-to-gitlab`	all versions	2.29`org.jenkins-ci.plugins:violation-comments-to-gitlab:2.29`

Affected Products

1 product · 1 configurations

Application

violation comments to gitlabjenkins

≤ 2.28

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:violation-comments-to-gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:violation-comments-to-gitlab to 2.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10416 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Violation Comments to GitLab Plugin stored API tokens unencrypted in job `config.xml` files and its global configuration file `org.jenkinsci.plugins.jvctgl.ViolationsToGitLabGlobalConfiguration.xml` on the Jenkins controller. These credentials could be viewed by users with Extended Read permission, or access to the Jenkins controller file system. Violation Comments to GitLab Plugin now stores these credentials encrypted. Existing jobs need to have their configuration saved for existing plain text credentials to be overwritten.

O3 Security · Impact-Aware SCA

Is CVE-2019-10416 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-522CWE-522

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 25, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-10416

GHSA-3p8r-p4q5-mc44

References

Advisoryopenwall.com Advisoryjenkins.io · 2019 09 25 Advisorynvd.nist.gov · CVE 2019 10416 Webgithub.com · e8237a803012bae7773d8bd10fe02e21892be3fe

Related vulnerabilities

Also affects violation-comments-to-gitlab

This CVE is medium severity, in line with the other 1 CVE affecting violation-comments-to-gitlab.

CVE-2019-10415

Same weakness: CWE-522

This CVE is medium severity; 7 of 7 other CVEs with CWE-522 are rated as high or higher (top: high).

CVE-2026-118763CVE-2026-116683GHSA-vqqp-x5qm-5qp4CVE-2026-111765CVE-2026-111763CVE-2026-113652CVE-2026-91982Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-10416 — violation-comments-to-git…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-10416 in your dependencies?