YAML file probing via unvalidated locale path
Published Jul 28, 2026 · Updated Jul 28, 2026
Path traversal in Pagy 43.0.0 through 43.5.5 allows remote attackers to probe the existence and readability of host YAML files. Pagy::I18n.locale= stores an assigned locale verbatim, and the loader joins it into a locale-named YAML path before YAML.load_file reads it. Exploitation requires an application to pass unsanitized end-user input to the setter; results reveal a YAML file's existence or readability, not its contents.
Summary
What happened
Path traversal in Pagy 43.0.0 through 43.5.5 allows remote attackers to probe the existence and readability of host YAML files. Pagy::I18n.locale= stores an assigned locale verbatim, and the loader joins it into a locale-named YAML path before YAML.load_file reads it. Exploitation requires an application to pass unsanitized end-user input to the setter; results reveal a YAML file's existence or readability, not its contents.
The record
- CVE
- CVE-2026-54659
- Published
- Jul 28, 2026
- Updated
- Jul 28, 2026
- Vendor
- ddnexus
- Product
- Pagy
- Classifications
- CWE-200, CWE-22, T1083
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Jul 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 43.0.0, < 43.5.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream YAML path traversal proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo