CVE-2026-70658: pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier

Published Sep 14, 2026
·
Updated

Pay is a payments engine for Ruby on Rails 6.0 and higher. Prior to 11.6.2, Pay::Webhooks::PaddleBillingController#validsignature? in app/controllers/pay/webhooks/paddlebillingcontroller.rb compares the computed 64-character SHA-256 HMAC with the attacker-controlled h1 token from the Paddle-Signature header using Ruby String#==. An unauthenticated remote attacker who can repeatedly submit requests to /pay/webhooks/paddlebilling and obtain sufficiently precise timing measurements can infer matching digest prefixes and recover a valid signature. A forged accepted webhook is enqueued through Pay::Webhooks::ProcessJob and can cause a host application to update billing state, provision paid features, record refunds, or trigger customer notifications. This issue is fixed in version 11.6.2.

Affected Software

1 affected component
pay-rails pay-rails/pay<11.6.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pay-rails/pay to a version that resolves this vulnerability.

    Fixed in 11.6.2Patch pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier

Event History

Sep 14, 2026
CVE Published
via MITRE·05:14 PM
Data Sourced
via MITRE·05:14 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:19 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What conditions must an attacker meet to forge an accepted webhook?

The attacker does not need authentication, but must be able to repeatedly send requests to /pay/webhooks/paddle_billing and obtain sufficiently precise timing measurements. They use those measurements to infer matching prefixes of the SHA-256 HMAC and recover a valid signature.

2

What application actions could a successful forged webhook cause?

An accepted forged webhook is enqueued through Pay::Webhooks::ProcessJob. Depending on the host application's webhook handling, it can update billing state, provision paid features, record refunds, or trigger customer notifications.

3

Which deployments are affected and what version fixes the issue?

Pay versions prior to 11.6.2 are affected where the Paddle Billing webhook signature verifier is used. Version 11.6.2 fixes the non-constant-time signature comparison.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203