VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

brakeman: vulnerability history, versions and safety

brakeman is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

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 brakeman vulnerabilities

Vulert verdict on brakeman 8.1.0 i

Updated on 23 Oct 2026

Good news: 8.1.0, the version you would install today, has no known vulnerabilities.

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 8.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 7,283 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by RubyGems, 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 brakeman, 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
8.1.0 01 Oct 2026 none non-standard — Details →
8.0.6 12 Aug 2026 none non-standard — Details →
8.0.5 12 Jun 2026 none non-standard — Details →
8.0.4 27 Feb 2026 none non-standard — Details →
8.0.3 26 Feb 2026 none non-standard — Details →
8.0.2 03 Feb 2026 none non-standard — Details →
8.0.1 30 Jan 2026 none non-standard — Details →
8.0.0 29 Jan 2026 none non-standard — Details →
7.1.2 25 Dec 2025 none non-standard — Details →
7.1.1 04 Nov 2025 none non-standard — Details →
7.1.0 18 Jul 2025 none non-standard — Details →
7.0.2 04 Apr 2025 none non-standard — Details →
7.0.1 04 Apr 2025 none non-standard — Details →
7.0.0 31 Dec 2024 none non-standard — Details →
6.2.2 18 Oct 2024 none non-standard — Details →
6.2.2.rc1 15 Oct 2024 none non-standard — Details →
6.2.1 22 Aug 2024 none non-standard — Details →
6.2.0 22 Aug 2024 none non-standard — Details →
6.1.2 02 Feb 2024 none non-standard — Details →
6.1.1 24 Dec 2023 none non-standard — Details →
6.1.0 05 Dec 2023 none non-standard — Details →
6.0.1 20 Jul 2023 none non-standard — Details →
6.0.0 25 May 2023 none non-standard — Details →
5.4.1 21 Feb 2023 none non-standard — Details →
5.4.0 18 Nov 2022 none non-standard — Details →
5.3.1 10 Aug 2022 none non-standard — Details →
5.3.0 10 Aug 2022 none non-standard — Details →
5.2.3 02 May 2022 none non-standard — Details →
5.2.2 06 Apr 2022 none non-standard — Details →
5.2.1 30 Jan 2022 none non-standard — Details →
5.2.0 16 Dec 2021 none non-standard — Details →
5.1.2 28 Oct 2021 none non-standard — Details →
5.1.1 20 Jul 2021 none non-standard — Details →
5.1.0 19 Jul 2021 none non-standard — Details →
5.0.4 08 Jun 2021 none non-standard — Details →
5.0.2 07 Jun 2021 none non-standard — Details →
5.0.1 28 Apr 2021 none non-standard — Details →
5.0.0 27 Jan 2021 none non-standard — Details →
4.10.1 25 Dec 2020 none non-standard — Details →
5.0.0.pre1 18 Nov 2020 none non-standard — Details →
4.10.0 28 Sep 2020 none non-standard — Details →
4.9.1 04 Sep 2020 none non-standard — Details →
4.9.0 04 Aug 2020 none non-standard — Details →
4.8.2 12 May 2020 none non-standard — Details →
4.8.1 07 Apr 2020 none non-standard — Details →
4.8.0 18 Feb 2020 none non-standard — Details →
4.7.2 25 Nov 2019 none non-standard — Details →
4.7.1 29 Oct 2019 none non-standard — Details →
4.7.0 16 Oct 2019 none non-standard — Details →
4.6.1 24 Jul 2019 none non-standard — Details →
4.6.0 23 Jul 2019 none non-standard — Details →
4.5.1 11 May 2019 none non-standard — Details →
4.5.0 16 Mar 2019 none non-standard — Details →
4.4.0 17 Jan 2019 none non-standard — Details →
4.3.1 07 Jun 2018 none MIT — Details →
4.3.0 11 May 2018 none MIT — Details →
4.2.1 24 Mar 2018 none MIT — Details →
4.2.0 22 Feb 2018 none MIT — Details →
4.1.1 19 Dec 2017 none MIT — Details →
4.1.0 14 Dec 2017 none MIT — Details →
4.0.1 25 Sep 2017 none MIT — Details →
4.0.1.pre1 25 Sep 2017 none MIT — Details →
4.0.0 25 Sep 2017 none MIT — Details →
3.7.2 16 Aug 2017 none MIT — Details →
3.7.1 16 Aug 2017 none MIT — Details →
3.7.0 30 Jun 2017 none MIT — Details →
3.6.2 19 May 2017 none MIT — Details →
3.6.1 24 Mar 2017 none MIT — Details →
3.6.0 23 Mar 2017 none MIT — Details →
3.5.0 01 Feb 2017 none MIT — Details →
3.4.1 02 Nov 2016 none MIT — Details →
3.4.0 08 Sep 2016 none MIT — Details →
3.3.5 12 Aug 2016 none MIT — Details →
3.3.4 12 Aug 2016 none MIT — Details →
3.3.3 21 Jul 2016 none MIT — Details →
3.3.2 10 Jun 2016 none MIT — Details →
3.3.1 03 Jun 2016 none MIT — Details →
3.3.0 05 May 2016 none MIT — Details →
3.2.1 25 Feb 2016 none MIT — Details →
3.2.0 25 Feb 2016 none MIT — Details →
3.2.0.pre1 22 Feb 2016 none MIT — Details →
3.1.5 28 Jan 2016 none MIT — Details →
3.1.4 22 Dec 2015 none MIT — Details →
3.1.3 03 Dec 2015 none MIT — Details →
3.1.2 28 Oct 2015 none MIT — Details →
3.1.1 23 Sep 2015 none MIT — Details →
3.1.0 31 Aug 2015 none MIT — Details →
3.0.5 20 Jun 2015 none MIT — Details →
3.0.4 18 Jun 2015 none MIT — Details →
3.0.3 30 Apr 2015 none MIT — Details →
3.0.2 09 Mar 2015 none MIT — Details →
3.0.1 23 Jan 2015 none MIT — Details →
3.0.0 03 Jan 2015 none MIT — Details →
2.6.3 14 Oct 2014 none MIT — Details →
2.6.2 18 Aug 2014 none MIT — Details →
2.6.1 02 Jul 2014 none MIT — Details →
2.6.0 06 Jun 2014 none MIT — Details →
2.5.0 30 Apr 2014 none MIT — Details →
2.4.3 23 Mar 2014 none MIT — Details →
2.4.2 21 Mar 2014 none MIT — Details →
2.4.1 19 Feb 2014 none — — Details →
2.4.0 05 Feb 2014 none — — Details →
2.3.1 13 Dec 2013 none — — Details →
2.3.0 12 Dec 2013 none — — Details →
2.2.0 28 Oct 2013 none — — Details →
2.1.2 18 Sep 2013 none — — Details →
2.1.1 21 Aug 2013 none — — Details →
2.1.0 17 Jul 2013 none — — Details →
2.0.0 20 May 2013 none — — Details →
2.0.0.pre2 16 May 2013 none — — Details →
1.9.5 05 Apr 2013 none — — Details →
1.9.4 19 Mar 2013 none — — Details →
1.9.3 01 Mar 2013 none — — Details →
1.9.2 14 Feb 2013 none — — Details →
1.9.1 19 Jan 2013 none — — Details →
1.9.0 25 Dec 2012 none — — Details →
1.9.0.pre2 24 Dec 2012 none — — Details →
1.9.0.pre1 21 Dec 2012 none — — Details →
1.8.3 13 Nov 2012 none — — Details →
1.8.2 17 Oct 2012 none — — Details →

The newest 120 of 169 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for brakeman

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 brakeman

Is brakeman safe to use?

Vulert has no vulnerabilities on record for brakeman in RubyGems at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is brakeman's Vulert package health score?

Vulert scores brakeman 88/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 brakeman affected?

No. 8.1.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 brakeman should I use?

8.1.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 brakeman have?

0 vulnerabilities are recorded for brakeman in the RubyGems ecosystem: 0 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 brakeman vulnerabilities disclosed?

0 vulnerabilities were recorded for brakeman in the last 12 months. 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 brakeman 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 brakeman for upcoming vulnerabilities?

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