CVE-2026-70658

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
49(Track*)
EG Risk 49/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 14, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v11.6.2

Patch available: pay-rails/pay v11.6.2

https://github.com/pay-rails/pay/releases/tag/v11.6.2
github_commit Patch Available

commit ba6494109d88 (pay-rails/pay)

Patch available: pay-rails/pay v11.6.2 (contains commit ba6494109d88)

https://github.com/pay-rails/pay/commit/ba6494109d88209fba2a4df2d9d6373fe81ed805
github Patch Available🟡 PoC Available

pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier (CWE-208) · Advisory · pay-rails/pay · GitHub

https://github.com/pay-rails/pay/security/advisories/GHSA-mjgf-xj26-9qf9

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
pay0.0.0 ... 9.0.1 (155 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 01:16 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 23:51 UTCEG score recompute
  4. 2026-09-16 22:20 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 09:31 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 08:02 UTCEG score recompute
  9. 2026-09-14 19:19 UTCEG score recompute
  10. 2026-09-14 19:05 UTCEG score recompute
  11. 2026-09-14 18:32 UTCEG score recompute
  12. 2026-09-14 17:21 UTCEG score recompute
  13. 2026-09-14 17:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-70658?
CVE-2026-70658 is a high vulnerability published on September 14, 2026. 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…
When was CVE-2026-70658 disclosed?
CVE-2026-70658 was first published in the National Vulnerability Database on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70658 actively exploited?
CVE-2026-70658 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.1% of all scored CVEs.
What is the CVSS score of CVE-2026-70658?
CVE-2026-70658 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-70658?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70658, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70658

Explore →

Is Your Infrastructure Affected by CVE-2026-70658?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs