Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:XCVSS 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-119420 is a high-severity Authentication Bypass Using an Alternate Path or Channel (CWE-288) vulnerability in Abraxaslabs (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique VNC (T1021.005); ranked at the 34th 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-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-113800
Vulnerability Data
Lago through 1.55.0 contains an authentication bypass vulnerability that allows organization administrators to obtain session tokens for existing accounts via the acceptInvite mutation without a password check. Attackers can invite a victim's email, accept with an arbitrary password, and receive…
more
a JWT to access the victim's organizations, billing data, API keys and payment integrations.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 3 OS baselines
V6.4.3V6.6.1V12.1.3
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Requires a tamperproof, always-invoked reference monitor that structurally blocks bypass via any alternate path.
Enforces authorization checks on every logical access path, eliminating unauthenticated alternate channels.
Mandates unique identification and authentication for all organizational users, covering the primary authentication requirement.
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.
Requiring authentication on every channel and path directly eliminates alternate-path bypasses.
Enforcing authorizations and least privilege across all access vectors prevents unauthenticated alternate paths.
Protecting networks and environments from unauthorized logical access blocks bypass via undocumented channels.
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.
Security testing can detect alternate-path bypasses but does not prevent them in production.
Access rights provisioning and review prevent bypass via unmonitored or alternate channels.
Privileged access rights control reduces risk of bypass through elevated or alternate paths.
A.8.20's network-level controls (firewalls per (i), network authentication per (h), connection filtering per (j)) can block exploitation of network-accessible alternate paths — e.g., a directly reachable web management URL or login screen — by restricting who reaches them, but cannot address local alternate paths (keyboard sequences, hardware registers), application-level alternate channels within the same service (API vs GUI), or design-level shadow resources, leaving a nameable remainder.
Secure coding practices help avoid bypass vulnerabilities but do not address deployed instances.
A.8.3 requires access restrictions (including no anonymous access and configuration mechanisms controlling access in systems, applications and services), which if well implemented would demand authentication on all paths and so block exploitation of an unauthenticated alternate channel; however, the weakness is a design flaw where the developer omitted authentication on a path, and A.8.3 is a policy/requirement clause whose blocking effect depends on the implementation of authentication mechanisms it does not itself enforce, leaving a nameable remainder of cases where the alternate path slips through.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (2 rules)
- V-248598 There must be no ".shosts" files on the OL 8 operating system. blocks CWE-288
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-288
Oracle Linux 9 (2 rules)
- V-271757 OL 9 file systems must not contain shosts.equiv files. blocks CWE-288
- V-271758 OL 9 file systems must not contain .shosts files. blocks CWE-288
RHEL 7 (2 rules, 1 more partial)
- V-204440 Red Hat Enterprise Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes. blocks CWE-288
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-288
- V-204424 The Red Hat Enterprise Linux operating system must not allow accounts configured with blank or null passwords. blocks CWE-288