VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

checkstyle: vulnerability history, versions and safety

checkstyle is a package in the OSS-Fuzz ecosystem. Vulert records 42 vulnerabilities for it across 37 releases, from Jul 2023 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
42 vulnerabilities recorded L42
i
14 with no fix published

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

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

Most recent disclosure 24 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all checkstyle vulnerabilities

Vulert verdict on checkstyle i

Updated on 23 Oct 2026

Careful: 14 of the 42 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 42 vulnerabilities on record across 2 years, 8 in the last year.

What to do: Plan around the 14 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 42 over 2 years · 8 in the last year i
  • Latest disclosure 24 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 14 i

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 holds for checkstyle, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 37 of 37 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 8
  • 2024 17
  • 2025 10
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for checkstyle

The 5 most severe of 42 vulnerabilities recorded for this package

Search all 42 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Exception in Checkstyle: Vulnerability in JavaLanguageParser N/A low No fix published 21 Jan 2026
Security Exception in com.puppycrawl.tools.checkstyle.JavaAstVisitor.getInnerBopAst N/A low 77b76ede17fb314d75db0f0e4ee0b86f2236daee 09 Feb 2024
Security Exception in Checkstyle Package: Vulnerability in JavaLanguageParser Statement Handling N/A low No fix published 24 May 2026
Security Exception in com.puppycrawl.tools.checkstyle.grammar.java.JavaLanguageParser.expr N/A low d335962fa743408b6823236cd5c352eb7ea7965a 15 May 2024
Security Exception in com.puppycrawl.tools.checkstyle.JavaAstVisitor.getInnerBopAst N/A low 977931a4c52791d55adce728106eef3766502e12 16 Aug 2024

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 checkstyle

Is checkstyle safe to use?

Vulert records 42 vulnerabilities for checkstyle in OSS-Fuzz: 0 critical, 0 high, 0 medium and 42 low. 14 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does checkstyle have?

42 vulnerabilities are recorded for checkstyle in the OSS-Fuzz ecosystem: 0 critical, 0 high, 0 medium and 42 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new checkstyle vulnerabilities disclosed?

8 vulnerabilities were recorded for checkstyle in the last 12 months, and the oldest entry in this database dates to 17 Jul 2023. 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 checkstyle 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 checkstyle for upcoming vulnerabilities?

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