{"answers":{"affected":"2 open source packages ship an affected version, including pay.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70658 exists.","fix":"No fix has been published for CVE-2026-70658 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-70658 is a high-severity vulnerability in pay-rails pay, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-70658 and fix it if it is affected.\n\nWhat it is: CVE-2026-70658 is a high-severity vulnerability in pay-rails pay, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70658 exists.\n\nAffected packages and fixed versions:\n- pay (RubyGems): affected all versions up to 11.6.1; no fix listed\n- pay (RubyGems): affected all versions up to 11.6.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-70658/ (Markdown: https://insights.sbomify.com/CVE-2026-70658/index.md)","id":"CVE-2026-70658","markdown":"https://insights.sbomify.com/CVE-2026-70658/index.md","name":"CVE-2026-70658","record":{"aliases":["GHSA-mjgf-xj26-9qf9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby on Rails payments library","requires_auth":"none","summary":"An attacker can bypass webhook signature verification via timing attacks to forge billing events, potentially granting unauthorized access to paid features or modifying customer data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Pay is a payments engine for Ruby on Rails 6.0 and higher. Prior to 11.6.2, Pay::Webhooks::PaddleBillingController#valid_signature? in app/controllers/pay/webhooks/paddle_billing_controller.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/paddle_billing 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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier","id":"CVE-2026-70658","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Doorkeeper OpenID Connect: DCR endpoint persists unvalidated client-supplied scopes","id":"CVE-2026-70665"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["11.6.1"],"package":"pay","purl":null,"source":"GHSA-mjgf-xj26-9qf9"},{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["11.6.1"],"package":"pay","purl":"pkg:gem/pay","source":"GHSA-mjgf-xj26-9qf9"}],"prev":{"headline":"Copyparty: file/dirkey confusion","id":"CVE-2026-70657"},"products":["pay"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["pay-rails"]},"summary":"An attacker can bypass webhook signature verification via timing attacks to forge billing events, potentially granting unauthorized access to paid features or modifying customer data.","url":"https://insights.sbomify.com/CVE-2026-70658/"}