CVE-2026-119422: juspay hyperswitch · Insufficient Verification of Data Authenticity
Affects juspay hyperswitchSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 2026.10.01.0 or 1.128.0 soon.
Data as of 30 Oct 2026, 12:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 2026.10.01.0, 1.128.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade juspay hyperswitch to 2026.10.01.0 or 1.128.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| juspayhyperswitch | Affected
| Fixed in
|
| juspayhyperswitch | Affected
| Fixed in
|
GitHubhyperswitchpkg:github/hyperswitchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Juspay Hyperswitch versions 1.128.0 and 2026.10.01.0. Users should upgrade to these versions or later to remediate the vulnerability. There is no indication that the vulnerability is mitigated by configuration or that no action is required.
Description
Juspay Hyperswitch versions before 1.128.0 contain an authentication bypass vulnerability in the Worldpayxml connector. The verify_webhook_source function always returns true without enforcing mutual TLS, allowing unauthenticated attackers who know the merchant_id and Worldpay orderCode to forge payment status updates. This can result in marking unpaid payments as charged or triggering refund, dispute, and payout events.
References
- github.com/juspay/hyperswitch/commit/681cf96bbc888239daf669a71b0554e934210ee3 (opens in a new tab)
- github.com/juspay/hyperswitch/commit/e797b36a1af204f4e4820c4938c6e4b10e9ae4fa (opens in a new tab)
- github.com/juspay/hyperswitch/blob/v1.127.0/crates/hyperswitch_connectors/src/connectors/worldpayxml.rs (opens in a new tab)
- github.com/juspay/hyperswitch/releases/tag/v1.128.0 (opens in a new tab)
- abraxaslabs.tech/research/hyperswitch-unsigned-webhook (opens in a new tab)
- github.com/juspay/hyperswitch (opens in a new tab)
- vulncheck.com/advisories/hyperswitch-before-1.128.0-webhook-authentication-bypass-via-worldpayxml-connector (opens in a new tab)