Read the docs
TI-2026-69041 Aliases CVE-2026-105811GHSA-r223-2773-wq4w

Authorization bypass in QnABot on AWS Amazon Q Business Lambda hook

Priority LOW 31CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

QnABot on AWS versions from 7.0.0 before 7.4.6 contain an authorization bypass in the optional Amazon Q Business Lambda hook sample. A flaw that trusts a user-controlled key (CWE-639) lets an authenticated remote user read arbitrary Amazon S3 objects in the deploying AWS account. The sample requires separate manual deployment and is not deployed automatically with QnABot, so customers who have not deployed it are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

Authorization bypass through a user-controlled key in the optional Amazon Q Business Lambda hook sample ( q-business-lambda-hook https://github.com/aws-solutions-library-samples/qnabot-on-aws/blob/main/source/docs/lambda_hooks/README.md ), available with QnABot on AWS versions 7.0.0 through 7.4.5, might allow an authenticated remote user to read arbitrary Amazon S3 objects in the deploying AWS account. This sample solution provides an example Lambda hook and requires separate, manual deployment and additional setup. It is not deployed automatically with QnABot. Customers who have not deployed this optional sample hook are not affected and do not need to take action. To remediate this issue, affected customers should update the QnABot on AWS stack to version 7.4.6 or later and then redeploy the Amazon Q Business Lambda hook sample stack. Updating the QnABot on AWS stack alone does not deliver the fix.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00333 26th percentileScored 2026-11-07
Fix Fixed qnabot-on-aws (aws): 7.4.6

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
AWSqnabot-on-aws7.0.0 to before 7.4.67.4.6Patch availableCNA
  • qnabot-on-aws VendorAWS Affected 7.0.0 to before 7.4.6 Fixed in 7.4.6 Patch available CNA

Remediation

Update the QnABot on AWS stack to version 7.4.6 or later, then redeploy the Amazon Q Business Lambda hook sample stack. Updating the QnABot on AWS stack alone does not deliver the fix.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA qnabot-on-aws (aws) Fixed in 7.4.6

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-105811
  2. 2026-10-07 Alias added: GHSA-r223-2773-wq4w
  3. 2026-10-07 CISA SSVC decision points changed
  4. 2026-10-07 Priority changed: MEDIUM → LOW

References

Patch 1

Advisory 1

  • TI-2026-23989 crypto: algif_aead - Revert to operating out-of-place KEVCVSS 3.1HIGH 7.8
  • TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
  • TI-2024-18648 Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM… CVSS 3.1CRITICAL 9.8
  • TI-2024-05929 Openssh: regresshion - race condition in ssh allows rce/dos CVSS 3.1HIGH 8.1
  • TI-2025-03847 Input validation issue in AWS Amplify Studio UI component properties CVSS 4.0CRITICAL 9.0
  • TI-2026-11603 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF CVSS 4.0HIGH 7.9
See all 383 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences