CVE-2026-7191

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper use of the static-eval npm package in the open source solution qnabot-on-aws versions 7.2.4 and earlier may allow an authenticated administrator to execute arbitrary code within the fulfillment Lambda execution context by injecting a crafted conditional chaining expression via the Content Designer interface, which bypasses the intended expression sandbox through JavaScript prototype manipulation. This may grant direct access to backend resources (Lambda environment variables, OpenSearch indices, S3 objects, DynamoDB tables) that are not exposed through normal administrative interfaces.

We recommend you upgrade to version 7.3.0 or above.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
34.8%
KEV
Not listed

Published

April 27, 2026

Last Modified

April 28, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github_release.
github_release Patch Available

v7.3.0

Patch available: aws-solutions/qnabot-on-aws v7.3.0

https://github.com/aws-solutions/qnabot-on-aws/releases/tag/v7.3.0
generic

CVE-2026-7191- Arbitrary Code Execution via Sandbox Bypass in QnABot on AWS

https://aws.amazon.com/security/security-bulletins/2026-020-aws/

Vendor Advisories for CVE-2026-7191(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:50 UTCEPSS rescore
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:26 UTCEPSS rescore
  25. 2026-06-19 19:26 UTCEPSS rescore
Show 61 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-17 17:53 UTCEPSS rescore
  4. 2026-06-16 17:53 UTCEPSS rescore
  5. 2026-06-15 17:49 UTCEPSS rescore
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-14 23:18 UTCEPSS rescore
  8. 2026-06-14 22:46 UTCEG score recompute
  9. 2026-06-14 10:53 UTCEG score recompute
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 04:49 UTCEG score recompute
  14. 2026-06-11 17:29 UTCEG score recompute
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-11 06:05 UTCEG score recompute
  17. 2026-06-10 22:19 UTCEPSS rescore
  18. 2026-06-10 13:22 UTCEPSS rescore
  19. 2026-06-10 12:58 UTCEG score recompute
  20. 2026-06-10 01:40 UTCEG score recompute
  21. 2026-06-09 14:21 UTCEG score recompute
  22. 2026-06-09 03:03 UTCEG score recompute
  23. 2026-06-08 14:54 UTCEG score recompute
  24. 2026-06-08 14:17 UTCEPSS rescore
  25. 2026-06-08 03:36 UTCEG score recompute
  26. 2026-06-07 16:18 UTCEG score recompute
  27. 2026-06-07 15:25 UTCEPSS rescore
  28. 2026-06-07 04:59 UTCEG score recompute
  29. 2026-06-06 17:41 UTCEG score recompute
  30. 2026-06-06 13:47 UTCEPSS rescore
  31. 2026-06-06 06:20 UTCEG score recompute
  32. 2026-06-05 22:47 UTCEPSS rescore
  33. 2026-06-05 19:00 UTCEG score recompute
  34. 2026-06-05 07:39 UTCEG score recompute
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-04 20:20 UTCEG score recompute
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 08:52 UTCEG score recompute
  39. 2026-06-03 20:16 UTCEG score recompute
  40. 2026-06-03 08:57 UTCEG score recompute
  41. 2026-06-02 21:32 UTCEG score recompute
  42. 2026-06-02 20:13 UTCEPSS rescore
  43. 2026-06-02 10:12 UTCEG score recompute
  44. 2026-06-01 22:53 UTCEG score recompute
  45. 2026-06-01 13:52 UTCEPSS rescore
  46. 2026-06-01 11:34 UTCEG score recompute
  47. 2026-05-31 22:30 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 13:44 UTCEPSS rescore
  50. 2026-05-29 13:44 UTCEPSS rescore
  51. 2026-05-28 13:44 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-27 13:40 UTCEPSS rescore
  54. 2026-05-27 13:40 UTCEPSS rescore
  55. 2026-05-26 13:44 UTCEPSS rescore
  56. 2026-05-26 07:18 UTCEPSS rescore
  57. 2026-05-23 00:08 UTCEG score recompute
  58. 2026-05-21 22:43 UTCEPSS rescore
  59. 2026-05-20 22:38 UTCEPSS rescore
  60. 2026-05-20 15:26 UTCEG score recompute
  61. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7191?
CVE-2026-7191 is a high vulnerability published on April 27, 2026. Improper use of the static-eval npm package in the open source solution qnabot-on-aws versions 7.2.4 and earlier may allow an authenticated administrator to execute arbitrary code within the fulfillment Lambda execution context by injecting a crafted conditional chaining expression via the Content…
When was CVE-2026-7191 disclosed?
CVE-2026-7191 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7191 actively exploited?
CVE-2026-7191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7191?
CVE-2026-7191 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-7191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7191, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-7191

Explore →

Is Your Infrastructure Affected by CVE-2026-7191?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs