VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

view_component: vulnerability history, versions and safety

view_component is a package in the RubyGems ecosystem. Vulert records 6 vulnerabilities for it across 59 releases, from Mar 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 15 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all view_component vulnerabilities

Vulert verdict on view_component 4.19.0 i

Updated on 22 Oct 2026

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

Package health score 80/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 4.19.0 — unaffected i
  • Vulnerabilities on record 6 over 4 years · 4 in the last year i
  • Latest disclosure 15 Jul 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Stars 3,571 i
  • Last release this month i
  • Licence MIT 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 view_component, 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
4.19.0 22 Oct 2026 none MIT — Details →
4.18.0 22 Oct 2026 none MIT — Details →
4.17.0 20 Oct 2026 none MIT — Details →
4.16.0 16 Oct 2026 none MIT — Details →
4.15.0 25 Aug 2026 none MIT — Details →
3.27.0 24 Aug 2026 M2 MIT Yes Details →
4.14.0 24 Aug 2026 none MIT — Details →
4.13.0 24 Aug 2026 none MIT — Details →
3.26.0 12 Aug 2026 M2 MIT Yes Details →
3.25.0 05 Jun 2026 M2 MIT Yes Details →
4.12.0 04 Jun 2026 none MIT — Details →
4.11.0 18 May 2026 H1 M1 MIT Yes Details →
4.10.0 11 May 2026 H1 M1 MIT Yes Details →
4.9.0 05 May 2026 H1 M1 MIT Yes Details →
4.8.0 22 Apr 2026 H1 M3 MIT Yes Details →
4.7.0 17 Apr 2026 H1 M3 MIT Yes Details →
4.6.0 30 Mar 2026 H1 M3 MIT Yes Details →
4.5.0 26 Feb 2026 H1 M3 MIT Yes Details →
4.4.0 13 Feb 2026 H1 M3 MIT Yes Details →
4.3.0 11 Feb 2026 H1 M3 MIT Yes Details →
4.2.0 09 Jan 2026 H1 M3 MIT Yes Details →
3.24.0 11 Nov 2025 M2 MIT Yes Details →
4.1.1 11 Nov 2025 H1 M3 MIT Yes Details →
4.1.0 22 Oct 2025 H1 M3 MIT Yes Details →
4.0.2 15 Aug 2025 H1 M3 MIT Yes Details →
4.0.1 05 Aug 2025 H1 M3 MIT Yes Details →
4.0.0 30 Jul 2025 H1 M3 MIT Yes Details →
4.0.0.rc5 22 Jul 2025 M2 MIT Yes Details →
4.0.0.rc4 21 Jul 2025 M2 MIT Yes Details →
4.0.0.rc3 18 Jul 2025 M2 MIT Yes Details →
4.0.0.rc2 03 Jul 2025 M2 MIT Yes Details →
4.0.0.rc1 23 Jun 2025 M2 MIT Yes Details →
4.0.0.alpha7 19 Jun 2025 M2 MIT Yes Details →
4.0.0.alpha6 03 Jun 2025 M2 MIT Yes Details →
3.23.2 23 May 2025 M2 MIT Yes Details →
3.23.1 22 May 2025 M2 MIT Yes Details →
3.23.0 21 May 2025 M2 MIT Yes Details →
4.0.0.alpha5 15 May 2025 M2 MIT Yes Details →
4.0.0.alpha4 14 May 2025 M2 MIT Yes Details →
4.0.0.alpha3 30 Apr 2025 M2 MIT Yes Details →
4.0.0.alpha2 25 Apr 2025 M2 MIT Yes Details →
4.0.0.alpha1 24 Apr 2025 M2 MIT Yes Details →
3.22.0 25 Mar 2025 M2 MIT Yes Details →
3.21.0 19 Dec 2024 M2 MIT Yes Details →
3.20.0 31 Oct 2024 M2 MIT Yes Details →
3.19.0 22 Oct 2024 M2 MIT Yes Details →
3.18.0 18 Oct 2024 M2 MIT Yes Details →
3.17.0 08 Oct 2024 M2 MIT Yes Details →
3.16.0 01 Oct 2024 M2 MIT Yes Details →
3.15.1 30 Sep 2024 M2 MIT Yes Details →
3.15.0 27 Sep 2024 M2 MIT Yes Details →
3.14.0 26 Aug 2024 M2 MIT Yes Details →
3.13.0 15 Jul 2024 M2 MIT Yes Details →
3.12.1 17 Apr 2024 M2 MIT Yes Details →
3.12.0 12 Apr 2024 M2 MIT Yes Details →
3.11.0 21 Feb 2024 M2 MIT Yes Details →
3.10.0 09 Jan 2024 M2 MIT Yes Details →
2.83.0 08 Jan 2024 none MIT — Details →
3.9.0 04 Jan 2024 M2 MIT Yes Details →
3.8.0 27 Nov 2023 M3 MIT Yes Details →
3.7.0 30 Oct 2023 M3 MIT Yes Details →
3.6.0 14 Sep 2023 M3 MIT Yes Details →
3.5.0 24 Jul 2023 M3 MIT Yes Details →
3.4.0 11 Jul 2023 M3 MIT Yes Details →
3.3.0 26 Jun 2023 M3 MIT Yes Details →
3.2.0 12 Jun 2023 M3 MIT Yes Details →
3.1.0 31 May 2023 M3 MIT Yes Details →
3.0.0 24 Apr 2023 M3 MIT Yes Details →
3.0.0.rc6 12 Apr 2023 none MIT — Details →
3.0.0.rc5 16 Mar 2023 none MIT — Details →
3.0.0.rc4 09 Mar 2023 none MIT — Details →
3.0.0.rc3 08 Mar 2023 none MIT — Details →
3.0.0.rc2 17 Feb 2023 none MIT — Details →
3.0.0.rc1 17 Jan 2023 none MIT — Details →
2.82.0 11 Jan 2023 none MIT — Details →
2.81.0 10 Jan 2023 none MIT — Details →
2.80.0 21 Dec 2022 none MIT — Details →
2.79.0 12 Dec 2022 none MIT — Details →
2.78.0 28 Nov 2022 none MIT — Details →
2.77.0 21 Nov 2022 none MIT — Details →
2.76.0 16 Nov 2022 none MIT — Details →
2.75.0 02 Nov 2022 none MIT — Details →
2.74.1 10 Oct 2022 none MIT — Details →
2.74.0 28 Sep 2022 none MIT — Details →
2.73.0 27 Sep 2022 none MIT — Details →
2.72.0 14 Sep 2022 none MIT — Details →
2.71.0 31 Aug 2022 none MIT — Details →
2.70.0 29 Aug 2022 none MIT — Details →
2.69.0 17 Aug 2022 none MIT — Details →
2.68.0 15 Aug 2022 none MIT — Details →
2.67.0 15 Aug 2022 none MIT — Details →
2.66.0 09 Aug 2022 none MIT — Details →
2.65.0 09 Aug 2022 none MIT — Details →
2.64.0 03 Aug 2022 none MIT — Details →
2.63.0 01 Aug 2022 none MIT — Details →
2.62.0 25 Jul 2022 none MIT — Details →
2.61.1 21 Jul 2022 none MIT — Details →
2.61.0 18 Jul 2022 none MIT — Details →
2.60.0 18 Jul 2022 none MIT — Details →
2.59.0 13 Jul 2022 none MIT — Details →
2.58.0 13 Jul 2022 none — — Details →
2.57.1 15 Jun 2022 none — — Details →
2.57.0 10 Jun 2022 none — — Details →
2.56.2 02 Jun 2022 none — — Details →
2.56.1 01 Jun 2022 none — — Details →
2.56.0 31 May 2022 none — — Details →
2.55.0 13 May 2022 none — — Details →
2.54.1 11 May 2022 none — — Details →
2.54.0 10 May 2022 none — — Details →
2.53.0 20 Apr 2022 none — — Details →
2.52.0 25 Mar 2022 none — — Details →
2.51.0 19 Mar 2022 none — — Details →
2.50.0 10 Mar 2022 none — — Details →
2.31.2 02 Mar 2022 none — — Details →
2.49.1 02 Mar 2022 none — — Details →
2.49.0 11 Feb 2022 none — — Details →
2.48.0 14 Jan 2022 none — — Details →
2.47.0 20 Dec 2021 none — — Details →
2.46.0 03 Dec 2021 none — — Details →
2.45.0 23 Nov 2021 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for view_component

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54498: ViewComponent HTML-Safety Bypass Vulnerability 8.7 high 4.12.0 15 Jul 2026
CVE-2022-24722: Cross-site Scripting Vulnerability in view_component 8.1 high 2.31.2 02 Mar 2022
CVE-2026-54497: ViewComponent Component Instances Retain Stale Render Context 6.8 medium 4.12.0 15 Jul 2026
CVE-2026-44836: view_component High Severity Vulnerability in Preview Route Dispatching 6.5 medium 4.9.0 08 May 2026
CVE-2024-21636: view_component Cross-site Scripting vulnerability 6.1 medium 3.9.0 04 Jan 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 view_component

Is view_component safe to use?

Vulert records 6 vulnerabilities for view_component in RubyGems: 0 critical, 2 high, 4 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 view_component's Vulert package health score?

Vulert scores view_component 80/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 view_component affected?

No. 4.19.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.

How many vulnerabilities does view_component have?

6 vulnerabilities are recorded for view_component in the RubyGems ecosystem: 0 critical, 2 high, 4 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 view_component vulnerabilities disclosed?

4 vulnerabilities were recorded for view_component in the last 12 months, and the oldest entry in this database dates to 02 Mar 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 view_component 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 view_component for upcoming vulnerabilities?

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