Hyperswitch before 1.128.0 Webhook Authentication Bypass via Worldpayxml Connector
Hyperswitch versions before 1.128.0 and before 2026.10.01.0 are affected when the Worldpayxml connector is used for webhooks, since its source check relies on mTLS. Fixed in 1.128.0 and 2026.10.01.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 1.128.0, 2026.10.01.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Juspay Hyperswitch before 1.128.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge payment status updates because the Worldpayxml connector's verify_webhook_source always returns true without enforced mTLS. Attackers knowing the merchant_id and Worldpay orderCode can POST unsigned XML with lastEvent SETTLED to the worldpayxml webhook endpoint, marking unpaid payments as charged or triggering refund, dispute and payout events.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- juspay hyperswitch
fixed in 1.128.0; fixed in 2026.10.01.0
References 7
GitHub · juspay/hyperswitch
abraxaslabs.tech
Questions about CVE-2026-119422
What does this mean?
The Worldpayxml connector's webhook handler skips its source verification step on the assumption that mTLS at the transport layer already verifies the sender. That leaves webhook authentication dependent on the transport layer alone.Source: github.com
Am I affected, and how do I check?
Affected versions are Hyperswitch before 1.128.0 and before 2026.10.01.0. The issue concerns setups that use the Worldpayxml connector for webhooks; to check a deployment, look at the installed Hyperswitch version and whether the Worldpayxml connector is configured.Source: github.com
What should I do about it?
Upgrade to Hyperswitch 1.128.0 or 2026.10.01.0, whichever line your deployment follows. The facts do not describe any other mitigation.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data