Information Disclosure in pagy (CVE-2026-54659)
Summary
Vulnerability in pagy (CVE-2026-54659). Risk of unauthorized operations or information disclosure. Exploitable via nil. Mitigation: upgrade to 43.5.6 or later.
Original description
The description as published by the source.
Pagy is agnostic pagination in plain Ruby. From 43.0.0 until 43.5.6, Pagy::I18n.locale= in gem/lib/pagy/modules/i18n/i18n.rb stored locale values verbatim and later used them as .yml path components, allowing untrusted params[:locale] values with absolute paths or ../ sequences to create a file existence and readability oracle for YAML files. This issue is fixed in version 43.5.6.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54659 has been found in pagy.
Attackers can target a specific entry point like nil over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pagy to 43.5.6 or later.
If unsure, ask your IT team or search "pagy CVE-2026-54659" on the vendor's site.
CVE-2026-54659 (pagy) — CWE-200
Attack surface: nil / YAML.load_file
Patched: 43.5.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in pagy. Attackers reach the vulnerable code path via nil.
Check the vendor advisory for the affected versions of pagy. Attack surface: nil / YAML.load_file.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 43.5.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pagy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pagy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pagyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pagy to 43.5.6ステージング環境で 43.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-54659 ruby-pagy
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com