Vulnerability Database · Maven · io.jenkins.plugins:code-coverage-api · Version

io.jenkins.plugins:code-coverage-api 1.1.0

1.1.0 is affected by 3 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.99.0.

Critical 0 High 2 Medium 1 Low 0 Unrated 0

Released 13 Feb 2024 Licence MIT Also known from other sources 3 Newer releases 64 Database updated 23/Oct/2026

Release and licence data published by Maven Central. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

io.jenkins.plugins:code-coverage-api 1.1.0 vulnerabilities

3 vulnerabilities cover io.jenkins.plugins:code-coverage-api 1.1.0. Open the full list in the database.

Looking for another version, or everything Vulert holds for io.jenkins.plugins:code-coverage-api?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.jenkins.plugins:code-coverage-api 1.1.0

Is io.jenkins.plugins:code-coverage-api 1.1.0 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover io.jenkins.plugins:code-coverage-api 1.1.0: 0 critical, 2 high, 1 medium and 0 low. The upgrade Vulert recommends is 4.99.0, and each entry above names the fixed version to move to.

Which version of io.jenkins.plugins:code-coverage-api should I use instead of 1.1.0?

4.99.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 1.1.0 the latest release of io.jenkins.plugins:code-coverage-api?

No. 1.1.0 was published 13 Feb 2024, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor io.jenkins.plugins:code-coverage-api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.jenkins.plugins:code-coverage-api version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.