CVE-2026-50218
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-50218 is a high-severity Resource Injection (CWE-99) vulnerability in Akamai GPA (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-100834
Vulnerability Data
Akamai GPA (Guardicore Platform Agent) client on all platforms before 7.4 improperly validates JWT tokens used for seeding. By convincing a user to interact with a malicious link, an attacker can use a spoofed JWT token to inject arbitrary parameters…
more
into the client software, resulting in unauthorized reconfiguration and full compromise of the application's functionality. This attack can also be targeted against an already seeded client if the attacker knows the URL of the IDP that the client used for enrollment.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, testing (scans/penetration), and developer training that reduce the chance of introducing resource injection flaws, but does not guarantee their absence at runtime and leaves a bounded remainder (e.g. incomplete enforcement of input restrictions or flaws in non-development phases).
Application security requirements explicitly call for controls on external identifiers used to access resources.
A.8.27 mandates security-by-design principles (e.g. distrust external input, least privilege, fail securely, data validation/sanitization) and design reviews that can stop resource injection from reaching production, but this is only a minority slice of CWE-99 because the control sets process expectations rather than mandating any specific runtime enforcement mechanism that would block exploitation of every possible identifier misuse.
Secure coding standards require strict validation and whitelisting of all resource identifiers before use.
Security testing can detect resource-injection flaws but does not itself implement preventive controls.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-99, a class-level weakness, and none of its children carries one either.