maven package report

Is io.jenkins.plugins:coverage safe?

1 known vulnerability, worst severity HIGH.

cvss
8.0

how bad it is if exploited, out of 10

epss
0.30%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-v3f3-rf6r-43x5, the advisory selected below

// advisories

GHSA-v3f3-rf6r-43x5

HIGHCVE-2025-67641

Jenkins Coverage Plugin 2.3054.ve1ff7baa123b and earlier does not validate the configured coverage results ID when creating coverage results, only when submitting the job configuration through the UI, allowing attackers with Item/Configure permission to use a javascript: scheme URL as identifier by configuring the job through the REST API, resulting in a stored cross-site scripting (XSS) vulnerabi

Affected
< 2.3056
Fixed in
2.3056
Weakness
CWE-79
Published
2025-12-10
Source
github

GHSANVDMITREreferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 03:46 UTC. The most recent advisory here was published 2025-12-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is io.jenkins.plugins:coverage safe? maven package security report | CyberXYZ