Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:htmlpublisher: vulnerability history, versions and safety

org.jenkins-ci.plugins:htmlpublisher is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 46 releases, from May 2022 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H3 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.jenkins-ci.plugins:htmlpublisher 429 i

Updated on 23 Oct 2026

Good news: 429, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

What to do: Stay on 429 or newer. This can change: a vulnerability disclosed tomorrow can affect 429 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 429 — unaffected i
  • Vulnerabilities on record 7 over 3 years · 1 in the last year i
  • Latest disclosure 29 Apr 2026 i
  • Highest CVSS 8.0 i
  • With no published fix 0 i
  • Stars 89 i
  • Last release 2 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for org.jenkins-ci.plugins:htmlpublisher, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
429 14 Aug 2026 none non-standard — Details →
428 09 Aug 2026 none non-standard — Details →
427.1 22 Apr 2026 none non-standard — Details →
427 02 Jul 2025 H1 non-standard Yes Details →
425 15 Mar 2025 H1 M1 non-standard Yes Details →
424.va_e57f1253461 26 Feb 2025 H1 M1 non-standard Yes Details →
1.37 13 Nov 2024 H1 M1 non-standard Yes Details →
1.36 16 Jul 2024 H1 M1 non-standard Yes Details →
1.35 26 Jun 2024 H1 M1 non-standard Yes Details →
1.34 28 May 2024 H1 M1 non-standard Yes Details →
1.33 07 Mar 2024 H1 M1 non-standard Yes Details →
1.32.1 07 Mar 2024 H1 M1 non-standard Yes Details →
1.15 13 Feb 2024 H2 M4 non-standard Yes Details →
1.3 13 Feb 2024 H2 M4 — Yes Details →
1.27 13 Feb 2024 H3 M2 non-standard Yes Details →
1.7 13 Feb 2024 H2 M4 non-standard Yes Details →
1.0 13 Feb 2024 H2 M4 — Yes Details →
1.32 13 Feb 2024 H3 M2 non-standard Yes Details →
1.24 13 Feb 2024 H3 M2 non-standard Yes Details →
1.18 13 Feb 2024 H3 M3 non-standard Yes Details →
1.9 13 Feb 2024 H2 M4 non-standard Yes Details →
1.16.1 13 Feb 2024 H3 M3 non-standard Yes Details →
1.25 13 Feb 2024 H3 M2 non-standard Yes Details →
1.5 13 Feb 2024 H2 M4 non-standard Yes Details →
1.1 13 Feb 2024 H2 M4 — Yes Details →
1.21 13 Feb 2024 H3 M2 non-standard Yes Details →
1.22-beta-1 13 Feb 2024 H3 M2 non-standard Yes Details →
1.13 13 Feb 2024 H2 M4 non-standard Yes Details →
1.19 13 Feb 2024 H3 M3 non-standard Yes Details →
1.8 13 Feb 2024 H2 M4 non-standard Yes Details →
1.10 13 Feb 2024 H2 M4 non-standard Yes Details →
1.14 13 Feb 2024 H2 M4 non-standard Yes Details →
1.4 13 Feb 2024 H2 M4 non-standard Yes Details →
1.20 13 Feb 2024 H3 M3 non-standard Yes Details →
0.8 13 Feb 2024 H2 M4 — Yes Details →
1.2 13 Feb 2024 H2 M4 — Yes Details →
1.16 13 Feb 2024 H3 M3 non-standard Yes Details →
1.28 13 Feb 2024 H3 M2 non-standard Yes Details →
1.23 13 Feb 2024 H3 M2 non-standard Yes Details →
1.30 13 Feb 2024 H3 M2 non-standard Yes Details →
1.11 13 Feb 2024 H2 M4 non-standard Yes Details →
1.31 13 Feb 2024 H3 M2 non-standard Yes Details →
0.7 13 Feb 2024 H2 M4 — Yes Details →
1.29 13 Feb 2024 H3 M2 non-standard Yes Details →
1.12 13 Feb 2024 H2 M4 non-standard Yes Details →
1.22 13 Feb 2024 H3 M2 non-standard Yes Details →
1.17 13 Feb 2024 H3 M3 non-standard Yes Details →
1.6 13 Feb 2024 H2 M4 non-standard Yes Details →
1.26 13 Feb 2024 H3 M2 non-standard Yes Details →

All 49 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 3
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 7 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 org.jenkins-ci.plugins:htmlpublisher

Is org.jenkins-ci.plugins:htmlpublisher safe to use?

Vulert records 7 vulnerabilities for org.jenkins-ci.plugins:htmlpublisher in Maven: 0 critical, 3 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.jenkins-ci.plugins:htmlpublisher's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:htmlpublisher 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.jenkins-ci.plugins:htmlpublisher affected?

No. 429, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.jenkins-ci.plugins:htmlpublisher should I use?

429 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.jenkins-ci.plugins:htmlpublisher have?

7 vulnerabilities are recorded for org.jenkins-ci.plugins:htmlpublisher in the Maven ecosystem: 0 critical, 3 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.jenkins-ci.plugins:htmlpublisher vulnerabilities disclosed?

1 vulnerability was recorded for org.jenkins-ci.plugins:htmlpublisher in the last 12 months, and the oldest entry in this database dates to 14 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.jenkins-ci.plugins:htmlpublisher are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.jenkins-ci.plugins:htmlpublisher for upcoming vulnerabilities?

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