Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25197 is a critical-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Mygardyn Cloud Api. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
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.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25197 is an authorization bypass vulnerability (CWE-639) in a specific API endpoint that allows authenticated users to pivot to other user profiles by modifying the ID number in the API call. Published on 2026-04-03, it carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). The vulnerability affects a component covered under CISA ICS Advisory ICSA-26-055-03, with details referenced on the vendor's security page at mygardyn.com/security/.
An attacker with authenticated access to the API can exploit this issue over the network with low complexity and no user interaction by altering the user ID parameter in requests. This enables unauthorized access to other users' profiles, resulting in high confidentiality and integrity impacts, such as viewing or potentially modifying sensitive profile data. The CVSS PR:N vector suggests no privileges may be required in some contexts, though the description specifies authenticated users.
CISA's ICS Advisory ICSA-26-055-03, along with the vendor security notice at mygardyn.com/security/ and the corresponding CSAF JSON file, provide guidance on mitigations, including patches or workarounds for affected systems. Security practitioners should consult these resources for specific remediation steps.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18831
Vulnerability Data
A specific endpoint allows authenticated users to pivot to other user profiles by modifying the id number in the API call.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.
Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.
Least-privilege restrictions limit the scope of data reachable even if a key check is bypassed.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.
Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.
Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.
Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.
Secure development lifecycle includes authorization design but does not itself implement runtime access checks.
Application security requirements can mandate authorization controls, yet the control itself is a requirements statement rather than an implemented safeguard.
Secure coding practices reduce the likelihood of missing authorization checks but do not guarantee their presence at runtime.