VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.jenkins.plugins:dingding-notifications: vulnerability history, versions and safety

io.jenkins.plugins:dingding-notifications is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 31 releases, from May 2022 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 L1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.jenkins.plugins:dingding-notifications vulnerabilities

Vulert verdict on io.jenkins.plugins:dingding-notifications 2.9.1 i

Updated on 23 Oct 2026

Careful: 2.9.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.9.1 — affected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 14 May 2025 i
  • Highest CVSS 5.9 i
  • With no published fix 1 i
  • Stars 363 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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 io.jenkins.plugins:dingding-notifications, 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
2.9.1 15 Sep 2026 M1 — No Details →
2.9.0 04 Sep 2026 M1 — No Details →
2.8.0 09 Jul 2025 M1 — No Details →
2.7.4 20 Jun 2025 M1 — No Details →
2.7.3 01 Mar 2024 M1 — No Details →
2.7.2 18 Feb 2024 M1 — No Details →
2.4.8 13 Feb 2024 M1 — No Details →
2.6.0 13 Feb 2024 M1 — No Details →
2.4.4 13 Feb 2024 M1 MIT No Details →
2.1.0 13 Feb 2024 M1 MIT No Details →
2.3.1 13 Feb 2024 M1 MIT No Details →
2.4.0 13 Feb 2024 M1 — No Details →
2.4.5 13 Feb 2024 M1 — No Details →
2.4.7 13 Feb 2024 M1 — No Details →
2.7.0 13 Feb 2024 M1 — No Details →
2.2.0 13 Feb 2024 M1 MIT No Details →
2.7.1 13 Feb 2024 M1 — No Details →
2.3.0 13 Feb 2024 M1 MIT No Details →
2.4.9 13 Feb 2024 M1 — No Details →
2.0.0 13 Feb 2024 M1 MIT No Details →
2.4.10 13 Feb 2024 M1 — No Details →
2.4.3 13 Feb 2024 M1 MIT No Details →
2.6.2 13 Feb 2024 M1 — No Details →
2.0.1 13 Feb 2024 M1 MIT No Details →
2.4.2 13 Feb 2024 M1 MIT No Details →
2.5.0 13 Feb 2024 M1 — No Details →
2.6.1 13 Feb 2024 M1 — No Details →
2.4.11 13 Feb 2024 M1 — No Details →
2.4.1 13 Feb 2024 M1 MIT No Details →
2.4.6 13 Feb 2024 M1 — No Details →
2.3.2 13 Feb 2024 M1 MIT No Details →

All 31 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 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for io.jenkins.plugins:dingding-notifications

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-47888: Jenkins DingTalk Plugin Unconditionally Disables SSL/TLS Certificate and Hostname Validation 5.9 medium No fix published 14 May 2025
CVE-2019-10433: DingTalk Plugin stores credentials in plain text 3.3 low 2.0.0 24 May 2022

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 io.jenkins.plugins:dingding-notifications

Is io.jenkins.plugins:dingding-notifications safe to use?

Vulert records 2 vulnerabilities for io.jenkins.plugins:dingding-notifications in Maven: 0 critical, 0 high, 1 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is io.jenkins.plugins:dingding-notifications's Vulert package health score?

Vulert scores io.jenkins.plugins:dingding-notifications 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of io.jenkins.plugins:dingding-notifications affected?

Yes. 2.9.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of io.jenkins.plugins:dingding-notifications should I use?

2.9.1 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 io.jenkins.plugins:dingding-notifications have?

2 vulnerabilities are recorded for io.jenkins.plugins:dingding-notifications in the Maven ecosystem: 0 critical, 0 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.jenkins.plugins:dingding-notifications vulnerabilities disclosed?

0 vulnerabilities were recorded for io.jenkins.plugins:dingding-notifications in the last 12 months, and the oldest entry in this database dates to 24 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 io.jenkins.plugins:dingding-notifications 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 io.jenkins.plugins:dingding-notifications for upcoming vulnerabilities?

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