VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.bcel:bcel: vulnerability history, versions and safety

org.apache.bcel:bcel is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 9 releases, first recorded in Nov 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 C1
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.

See all org.apache.bcel:bcel vulnerabilities

Vulert verdict on org.apache.bcel:bcel 6.13.0 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 6.13.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 Nov 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 130 packages i
  • Last release 1 month ago i
  • Licence Apache-2.0 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.apache.bcel:bcel, 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
6.13.0 06 Sep 2026 none Apache-2.0 — Details →
6.12.0 18 Jan 2026 none Apache-2.0 — Details →
6.11.0 09 Oct 2025 none Apache-2.0 — Details →
6.10.0 13 Jul 2024 none Apache-2.0 — Details →
6.9.0 21 Apr 2024 none Apache-2.0 — Details →
6.8.2 21 Feb 2024 none Apache-2.0 — Details →
6.8.1 07 Jan 2024 none Apache-2.0 — Details →
6.8.0 03 Dec 2023 none Apache-2.0 — Details →
6.7.0 28 Nov 2022 none Apache-2.0 — Details →
6.6.1 29 Oct 2022 none Apache-2.0 — Details →
6.6.0 08 Oct 2022 none Apache-2.0 — Details →
6.5.0 05 Jun 2020 C1 Apache-2.0 Yes Details →
6.4.1 27 Sep 2019 C1 Apache-2.0 Yes Details →
6.4.0 20 Sep 2019 C1 Apache-2.0 Yes Details →
6.3.1 21 Mar 2019 C1 Apache-2.0 Yes Details →
6.3 24 Jan 2019 C1 Apache-2.0 Yes Details →
6.2 30 Nov 2017 C1 Apache-2.0 Yes Details →
6.1 14 Sep 2017 C1 Apache-2.0 Yes Details →
6.0 10 Jul 2016 C1 Apache-2.0 Yes Details →
5.2 08 Jun 2006 C1 — Yes Details →

All 20 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.apache.bcel:bcel

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-42920: Apache Commons BCEL out-of-bounds write vulnerability 9.8 critical 6.6.0 07 Nov 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 org.apache.bcel:bcel

Is org.apache.bcel:bcel safe to use?

Vulert records 1 vulnerabilities for org.apache.bcel:bcel in Maven: 1 critical, 0 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.apache.bcel:bcel's Vulert package health score?

Vulert scores org.apache.bcel:bcel 87/100, which reads as healthy. 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.apache.bcel:bcel affected?

No. 6.13.0, 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.apache.bcel:bcel should I use?

6.13.0 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.apache.bcel:bcel have?

1 vulnerability is recorded for org.apache.bcel:bcel in the Maven ecosystem: 1 critical, 0 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.apache.bcel:bcel vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.bcel:bcel in the last 12 months, and the oldest entry in this database dates to 07 Nov 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.apache.bcel:bcel 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.apache.bcel:bcel for upcoming vulnerabilities?

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