# CVE-2026-119422: Hyperswitch before 1.128.0 Webhook Authentication Bypass via Worldpayxml Connector


- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-73m6-3vjm-8pf5

## What is CVE-2026-119422?

CVE-2026-119422 is a high-severity vulnerability in juspay hyperswitch, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-119422?


## How do I fix CVE-2026-119422?

No fix has been published for CVE-2026-119422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119422 being exploited?

There is no known exploitation of CVE-2026-119422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119422 and fix it if it is affected.

What it is: CVE-2026-119422 is a high-severity vulnerability in juspay hyperswitch, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119422 in the wild and no public exploit code.

Affected product: juspay hyperswitch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119422/ (Markdown: https://insights.sbomify.com/CVE-2026-119422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119422
- OSV: https://osv.dev/vulnerability/CVE-2026-119422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119422/
Summaries are generated and may contain mistakes; the official description above is the record.