VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

pay: vulnerability history, versions and safety

pay is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Apr 2023 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
2 vulnerabilities recorded H2
i
1 with no fix published

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

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

Most recent disclosure 01 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pay vulnerabilities

Vulert verdict on pay 12.3.0 i

Updated on 23 Oct 2026

Careful: 12.3.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 12.3.0 — affected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 01 Jul 2026 i
  • Highest CVSS 7.4 i
  • With no published fix 1 i
  • Stars 2,263 i
  • OpenSSF scorecard 3/10 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 pay, 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
12.3.0 06 Oct 2026 H1 MIT No Details →
12.2.0 02 Oct 2026 H1 MIT No Details →
12.1.1 26 Sep 2026 H1 MIT No Details →
12.1.0 21 Sep 2026 H1 MIT No Details →
12.0.0 21 Sep 2026 H1 MIT No Details →
11.8.0 20 Sep 2026 H1 MIT No Details →
11.7.2 23 Aug 2026 H1 MIT No Details →
11.7.1 13 Aug 2026 H1 MIT No Details →
11.7.0 30 Jul 2026 H1 MIT No Details →
11.6.2 06 Jul 2026 H1 MIT No Details →
11.6.1 08 Apr 2026 H1 MIT No Details →
11.6.0 31 Mar 2026 H1 MIT No Details →
11.5.0 30 Mar 2026 H1 MIT No Details →
11.4.3 23 Dec 2025 H1 MIT No Details →
11.4.2 23 Dec 2025 H1 MIT No Details →
11.4.1 10 Dec 2025 H1 MIT No Details →
11.4.0 25 Nov 2025 H1 MIT No Details →
11.3.1 10 Nov 2025 H1 MIT No Details →
11.3.0 03 Nov 2025 H1 MIT No Details →
11.2.3 28 Sep 2025 H1 MIT No Details →
11.2.2 13 Aug 2025 H1 MIT No Details →
11.2.1 06 Aug 2025 H1 MIT No Details →
11.2.0 02 Aug 2025 H1 MIT No Details →
11.1.3 30 Jul 2025 H1 MIT No Details →
11.1.2 29 Jul 2025 H1 MIT No Details →
11.1.1 13 Jun 2025 H1 MIT No Details →
11.1.0 09 Jun 2025 H1 MIT No Details →
11.0.1 05 Jun 2025 H1 MIT No Details →
11.0.0 04 Jun 2025 H1 MIT No Details →
10.1.5 01 Jun 2025 H1 MIT No Details →
10.1.4 01 Jun 2025 H1 MIT No Details →
10.1.3 06 May 2025 H1 MIT No Details →
10.1.2 01 May 2025 H1 MIT No Details →
10.1.1 30 Apr 2025 H1 MIT No Details →
10.1.0 29 Apr 2025 H1 MIT No Details →
10.0.4 23 Apr 2025 H1 MIT No Details →
10.0.3 23 Apr 2025 H1 MIT No Details →
10.0.2 22 Apr 2025 H1 MIT No Details →
10.0.1 22 Apr 2025 H1 MIT No Details →
10.0.0 18 Apr 2025 H1 MIT No Details →
9.0.1 27 Mar 2025 H1 MIT No Details →
9.0.0 27 Mar 2025 H1 MIT No Details →
8.3.0 20 Dec 2024 H1 MIT No Details →
8.2.2 13 Dec 2024 H1 MIT No Details →
8.2.1 26 Nov 2024 H1 MIT No Details →
8.2.0 19 Nov 2024 H1 MIT No Details →
8.1.3 29 Oct 2024 H1 MIT No Details →
8.1.2 14 Oct 2024 H1 MIT No Details →
8.1.1 04 Oct 2024 H1 MIT No Details →
8.1.0 02 Oct 2024 H1 MIT No Details →
8.0.0 23 Sep 2024 H1 MIT No Details →
7.3.0 09 Jul 2024 H1 MIT No Details →
7.2.1 29 May 2024 H1 MIT No Details →
7.2.0 16 May 2024 H1 MIT No Details →
7.1.1 12 Jan 2024 H1 MIT No Details →
7.1.0 06 Dec 2023 H1 MIT No Details →
7.0.0 06 Dec 2023 H1 MIT No Details →
6.8.1 05 Sep 2023 H1 MIT No Details →
6.8.0 22 Aug 2023 H1 MIT No Details →
6.7.2 17 Aug 2023 H1 MIT No Details →
6.7.1 28 Jul 2023 H1 MIT No Details →
6.7.0 18 Jul 2023 H1 MIT No Details →
6.6.1 02 Jun 2023 H1 MIT No Details →
6.6.0 02 Jun 2023 H1 MIT No Details →
6.5.0 17 May 2023 H1 MIT No Details →
6.4.0 13 May 2023 H1 MIT No Details →
6.3.4 02 May 2023 H1 MIT No Details →
6.3.3 21 Apr 2023 H1 MIT No Details →
6.3.2 19 Apr 2023 H1 MIT No Details →
6.3.1 13 Jan 2023 H2 MIT No Details →
6.3.0 13 Jan 2023 H2 MIT No Details →
6.2.4 09 Jan 2023 H2 MIT No Details →
6.2.3 05 Jan 2023 H2 MIT No Details →
6.2.2 05 Jan 2023 H2 MIT No Details →
6.2.1 04 Jan 2023 H2 MIT No Details →
6.2.0 23 Dec 2022 H2 MIT No Details →
6.1.2 17 Dec 2022 H2 MIT No Details →
6.1.1 14 Dec 2022 H2 MIT No Details →
6.1.0 26 Nov 2022 H2 MIT No Details →
6.0.3 22 Nov 2022 H2 MIT No Details →
6.0.2 22 Nov 2022 H2 MIT No Details →
6.0.1 22 Nov 2022 H2 MIT No Details →
6.0.0 21 Nov 2022 H2 MIT No Details →
5.0.4 29 Sep 2022 H2 MIT No Details →
5.0.3 19 Aug 2022 H2 MIT No Details →
5.0.2 18 Aug 2022 H2 MIT No Details →
5.0.1 04 Aug 2022 H2 MIT No Details →
5.0.0 04 Aug 2022 H2 MIT No Details →
4.2.1 04 Aug 2022 H2 MIT No Details →
4.2.0 29 Jul 2022 H2 MIT No Details →
4.1.1 29 Jul 2022 H2 MIT No Details →
4.1.0 28 Jul 2022 H2 MIT No Details →
4.0.4 28 Jul 2022 H2 MIT No Details →
4.0.2 27 Jul 2022 H2 MIT No Details →
4.0.1 07 Jun 2022 H2 MIT No Details →
4.0.0 10 May 2022 H2 MIT No Details →
3.0.24 02 Dec 2021 H2 MIT No Details →
3.0.23 07 Oct 2021 H2 MIT No Details →
3.0.22 03 Oct 2021 H2 MIT No Details →
3.0.21 16 Sep 2021 H2 MIT No Details →
3.0.20 16 Sep 2021 H2 — No Details →
3.0.19 15 Sep 2021 H2 — No Details →
3.0.18 15 Sep 2021 H2 — No Details →
3.0.17 14 Sep 2021 H2 — No Details →
3.0.16 11 Sep 2021 H2 — No Details →
3.0.15 11 Sep 2021 H2 — No Details →
3.0.14 11 Sep 2021 H2 — No Details →
3.0.13 11 Sep 2021 H2 — No Details →
3.0.12 08 Sep 2021 H2 — No Details →
3.0.11 07 Sep 2021 H2 — No Details →
3.0.10 05 Sep 2021 H2 — No Details →
3.0.9 05 Sep 2021 H2 — No Details →
3.0.8 05 Sep 2021 H2 — No Details →
3.0.7 05 Sep 2021 H2 — No Details →
3.0.6 04 Sep 2021 H2 — No Details →
3.0.5 04 Sep 2021 H2 — No Details →
3.0.4 03 Sep 2021 H2 — No Details →
3.0.2 03 Sep 2021 H2 — No Details →
3.0.1 02 Sep 2021 H2 — No Details →
3.0.0 01 Sep 2021 H2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pay

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Timing Attack Vulnerability in Pay Gem: Non-Constant-Time HMAC Comparison 7.4 high No fix published 01 Jul 2026
CVE-2023-30614: Cross-site Scripting (XSS) in Pay 7.1 high 6.3.2 20 Apr 2023

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 pay

Is pay safe to use?

Vulert records 2 vulnerabilities for pay in RubyGems: 0 critical, 2 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pay's Vulert package health score?

Vulert scores pay 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of pay affected?

Yes. 12.3.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of pay should I use?

12.3.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 pay have?

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

1 vulnerability was recorded for pay in the last 12 months, and the oldest entry in this database dates to 20 Apr 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 pay 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 pay for upcoming vulnerabilities?

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