Skip to main content
VulnerabilityPublished

CVE-2026-119421: juspay hyperswitch · Insecure Direct Object Reference

Affects juspay hyperswitchSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2026.10.19.0 soon.

Data as of 30 Oct 2026, 12:04 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
CNACVSS 4.08.2
Patch
Available – fixed in 2026.10.19.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.19.0.

Affected software

ProductAffectedFixed in
juspayhyperswitchAffected
  • <=1.128.0
  • <2026.10.19.0
Fixed in
  • 2026.10.19.0
GitHubhyperswitchpkg:github/hyperswitchOther threatsAffected
  • <=1.128.0
  • <2026.10.19.0
Fixed in
  • 2026.10.19.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Juspay Hyperswitch to version 2026.10.19.0 or later, where this authorization bypass vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

Juspay Hyperswitch versions up to 1.128.0 and builds before 2026.10.19.0 contain an authorization bypass vulnerability. This flaw allows unauthenticated attackers who possess the merchant's publishable key and a payout ID to confirm payouts via the POST /payouts/{payout_id}/confirm endpoint. Attackers can overwrite payout details such as amount, currency, connector, and routing, enabling unauthorized merchant payouts. The issue is fixed in version 2026.10.19.0.

References

Community reviews

Loading reviews…