Cyber Resilience

CVE-2026-19311

Published
12 August 2026
Modified
13 August 2026
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/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:X
EPSS Score 0.0042 35th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2026-19311 is a high-severity Undefined Behavior for Input to API (CWE-475) vulnerability in Amazon OpenSearch Alerting (inferred from references). Its CVSS base score is 8.6 (High).

Operationally, ranked at the 35th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Missing authorization in the Execute Monitor API in Amazon OpenSearch Alerting plugin might allow an authenticated remote user to read, modify, or delete arbitrary index data via a crafted inline monitor request with unintentional data source and input index parameters.

CWE(s)
CWE-475

Related Threats

CVEs Like This One

CVE-2023-52533Shared CWE-475
CVE-2024-20380Shared CWE-475
CVE-2026-42009Shared CWE-475
CVE-2025-47865Shared CWE-475
CVE-2023-4875Shared CWE-475
CVE-2023-2253Shared CWE-475
CVE-2025-47866Shared CWE-475
CVE-2024-3099Shared CWE-475
CVE-2024-10569Shared CWE-475
CVE-2023-4874Shared CWE-475

Affected Assets

Amazon
OpenSearch Alerting
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover calls that supply invalid control-parameter values before deployment.

SI-10 Information Input Validation good match

Validating inputs to API control parameters ensures only permitted values are supplied, structurally eliminating the source of undefined behavior.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices (coding standards, reviews, testing) directly prevent undefined behavior from invalid API inputs.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record this class of API-related weakness.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect undefined behavior from invalid API inputs before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes API specification and validation that can prevent undefined behavior from invalid inputs.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit input validation and defined behavior for API parameters.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles can require defensive coding that eliminates undefined behavior in APIs.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses avoiding undefined behavior by enforcing defined inputs and error handling in APIs.

References