CVE-2026-7191
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceqnabot-on-aws versions 7.2.4 and earlier use the static-eval npm package insecurely in the Content Designer interface. Authenticated administrators can inject malicious conditional chaining expressions that bypass the expression sandbox via JavaScript prototype manipulation, enabling arbitrary code execution within the fulfillment Lambda context and unauthorized access to backend AWS resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm qnabot-on-aws installationCheck the deployed AWS CloudFormation stacks or Lambda functions for 'qnabot' or 'QNAbot' naming patterns. Inspect the AWS console or CLI for resources tagged with the qnabot-on-aws solution.Affected if The environment does not contain any qnabot-on-aws resources
-
Identify the qnabot-on-aws versionCheck the version of the deployed qnabot-on-aws. This is typically visible in the CloudFormation stack outputs, the Lambda function metadata, or the AWS Solutions implementation documentation. Look for the version field in the main Lambda layer or stack details.Affected if The installed version is 7.2.4 or any version earlier than 7.2.4 (e.g., 7.2.3, 7.2.0, 7.1.x, etc.)
-
Verify Content Designer interface is accessibleCheck if the qnabot-on-aws Content Designer UI is enabled and accessible. This is typically accessed via the qnabot console or the /designer endpoint. Inspect IAM policies and Cognito user pool settings to confirm administrator users exist.Affected if The Content Designer interface is enabled and administrator users have access to it
-
Inspect static-eval usage in Content Designer LambdaExamine the Lambda function handling Content Designer requests (typically named something like 'QNA-ContentDesigner' or 'qnabot-content-designer'). Look for the static-eval npm package in the function's package dependencies or source code.Affected if The Content Designer Lambda contains or imports the static-eval package and uses it to evaluate user-provided expressions
-
Check for expression sandbox implementationReview the Content Designer code for any expression evaluation logic. Identify if a sandbox or allowlist is used to restrict evaluated expressions, and whether prototype manipulation checks are present.Affected if Expressions from the Content Designer interface are evaluated without proper prototype pollution safeguards or sandboxing
A user is affected if qnabot-on-aws version 7.2.4 or earlier is deployed, the Content Designer interface is accessible to administrators, and the static-eval package is used to process conditional expressions without prototype pollution protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade qnabot-on-aws to version 7.3.0 or later to replace the vulnerable static-eval implementation with a secure alternative.
version 7.3.0 or latest stable release
- Back up your current qnabot-on-aws deployment configuration and any custom content
- Download or access qnabot-on-aws version 7.3.0 or the latest stable release from the official GitHub repository
- If using AWS CloudFormation, update your CloudFormation stack template to reference version 7.3.0 or use the latest AWS Quick Start template
- Redeploy the qnabot-on-aws solution by updating the CloudFormation stack or running the deployment scripts
- Verify the upgrade by logging into the Content Designer interface and testing that the static-eval vulnerability is mitigated
- Confirm that normal qnaBot functionality works as expected after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data