Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:yaml-axis is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 4 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on org.jenkins-ci.plugins:yaml-axis 418.v1512370c17e3 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 418.v1512370c17e3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 4 i
  • Last release 2 months ago i
  • Licence MIT 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:yaml-axis, 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
418.v1512370c17e3 06 Aug 2026 none — — Details →
412.v0604894152d0 24 Jul 2026 none — — Details →
384.v3ff947797a_88 27 Jan 2026 none — — Details →
380.v09eb_4d50d200 05 Jan 2026 none — — Details →
370.vef22e32ca_b_87 20 Dec 2025 none — — Details →
330.vb_fecb_eccb_7d2 16 Aug 2025 none — — Details →
306.v5302614360b_e 17 May 2025 none — — Details →
298.v03a_fd268f957 03 May 2025 none — — Details →
278.vb_9ea_68c30a_b_8 08 Mar 2025 none — — Details →
276.v2eddea_407e27 03 Mar 2025 none — — Details →
257.v09b_85104197d 12 Oct 2024 none — — Details →
249.v51e722923ee6 31 Aug 2024 none — — Details →
243.vf6b_e381967a_c 24 Aug 2024 none — — Details →
229.v42d9dfe8a_655 06 Jul 2024 none — — Details →
225.v84212ee9df02 27 Jun 2024 none — — Details →
215.v61fca_2940177 08 Jun 2024 none — — Details →
173.v83f01b_a_9e6c8 05 Mar 2024 none — — Details →
169.v3f674a_9da_e9b_ 27 Feb 2024 none — — Details →
0.2.1 13 Feb 2024 none — — Details →
0.2.2 13 Feb 2024 none — — Details →
0.2.0 13 Feb 2024 H1 — Yes Details →
0.1.1 13 Feb 2024 H1 — Yes Details →
0.1.2 13 Feb 2024 H1 — Yes Details →
0.3.0 13 Feb 2024 none — — Details →
0.1.0 13 Feb 2024 H1 — Yes Details →

All 25 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

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:yaml-axis

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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:yaml-axis

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

Vulert records 1 vulnerabilities for org.jenkins-ci.plugins:yaml-axis in Maven: 0 critical, 1 high, 0 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:yaml-axis's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:yaml-axis 70/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:yaml-axis affected?

No. 418.v1512370c17e3, 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:yaml-axis should I use?

418.v1512370c17e3 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:yaml-axis have?

1 vulnerability is recorded for org.jenkins-ci.plugins:yaml-axis in the Maven ecosystem: 0 critical, 1 high, 0 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:yaml-axis vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:yaml-axis 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 org.jenkins-ci.plugins:yaml-axis 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:yaml-axis for upcoming vulnerabilities?

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