Security Resilience

CVE-2026-119421

Access Control

Public PoCAccess Control
Published
30 October 2026
Modified
30 October 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0034 28th percentile
Risk Priority 34 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-119421 is a high-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Abraxaslabs (inferred from references). Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Databases (T1213.006); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Juspay Hyperswitch through 1.128.0 (and builds before 2026.10.19.0) contains a missing authorization vulnerability that allows unauthenticated attackers to confirm payouts with any client_secret via POST /payouts/{payout_id}/confirm. Attackers holding the merchant's publishable key and a payout_id can confirm payouts and overwrite…

more

amount, currency, connector, and routing fields to trigger unauthorized merchant payouts.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1213.006 Databases Collection
Adversaries may leverage databases to mine valuable information.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-59190Shared CWE-639
CVE-2026-80254Shared CWE-639
CVE-2026-29189Shared CWE-639
CVE-2026-12657Shared CWE-639
CVE-2024-1313Shared CWE-639
CVE-2025-10493Shared CWE-639
CVE-2026-78064Shared CWE-639
CVE-2024-52601Shared CWE-639
CVE-2026-9341Shared CWE-639
CVE-2026-34592Shared CWE-639

Affected Assets

Abraxaslabs
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.

Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.AA-05 full match
blocks

Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.

PR.IR-01 mostly match
blocks

Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

removes

A.8.3 mandates that access to information be restricted based on user identity and permissions, directly addressing the missing authorization check that defines CWE-639; when applied, it removes the vulnerability by requiring that such checks be implemented.

finds

Security testing can detect missing authorization checks but does not prevent the weakness in production.

blocks

Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.

prevents

Secure coding practices reduce the likelihood of missing authorization checks but do not guarantee their presence at runtime.

References