AWS VDP
By Amazon Web Services Vulnerability disclosure program on HackerOne amazon.com
Accepting reports
Full safe harbor
- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 552
- Public CVEs
- 60
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report through their form
- hackerone.com/aws_vdp
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 1 day
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 1 days
You will receive a non-automated response confirming receipt of your initial report within 24 hours, timely updates, and monthly check-ins throughout the engagement.
- Safe harbor
-
Full
We consider Good Faith Security Research to be authorized activity that is protected from adversarial legal action by us.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
552 assets you may test, 1 excluded.
Wildcard domains 17
- *.agscollab.com Critical No bounty
- *.agslauncher.com Critical No bounty
- *.amazongames.com Critical No bounty
- *.aws.dev Critical No bounty
- *.cloudendure.com Critical No bounty
- *.gaming.amazon.com Critical No bounty
- github.com/awslabs/* Informational No bounty
- github.com/deepjavalibrary/* Critical No bounty
- github.com/strands-agents/* Critical No bounty
- *.lambda-url.*.on.aws Critical No bounty
- *.lostark.games.aws.dev High No bounty
- *.newworld.com Critical No bounty
- *.people.aws.com Low No bounty
- *.people.aws.dev Low No bounty
- *.sa.aws.dev Informational No bounty
- *.tsologic.com Critical No bounty
- *.workshops.aws.dev Medium No bounty
Source code 10
- https://github.com/amazonlinux/amazon-linux-2023 Critical No bounty
- https://github.com/aws-actions/* Critical No bounty
- https://github.com/aws/amazon-ecs-agent Critical No bounty
- https://github.com/aws/amazon-ecs-cli Critical No bounty
- https://github.com/aws/amazon-vpc-cni-k8s Critical No bounty
- https://github.com/aws/aws-cdk Critical No bounty
- https://github.com/aws/aws-cli Critical No bounty
- https://github.com/aws/aws-sdk Critical No bounty
- https://github.com/aws/s2n-quic Critical No bounty
- https://github.com/aws/s2n-tls Critical No bounty
Web 3
- forums.newworld.com Critical No bounty
- https://github.com/aws-samples Critical No bounty
- www.awseducate.com Critical No bounty
APIs 1
- All API's called by the AWS CLI Critical No bounty
iOS apps 1
- 1023499075 Critical No bounty
Products and areas 520
- Alexa For Business Critical No bounty
- Amazon AI Operations Critical No bounty
- Amazon API Gateway Critical No bounty
- Amazon AppFlow Critical No bounty
- Amazon AppIntegrations Critical No bounty
- Amazon AppStream Critical No bounty
- Amazon AppStream 2.0 Critical No bounty
- Amazon Athena Critical No bounty
- Amazon Augmented AI (Amazon A2I) Critical No bounty
- Amazon Aurora Critical No bounty
- Amazon Aurora DSQL Critical No bounty
- Amazon Bedrock Critical No bounty
- Amazon Braket Critical No bounty
- Amazon Chime Critical No bounty
- Amazon Chime SDK Critical No bounty
- Amazon Cloud Directory Critical No bounty
- Amazon CloudFront Critical No bounty
- Amazon CloudSearch Critical No bounty
- Amazon CloudWatch Critical No bounty
- Amazon CloudWatch Application Insights Critical No bounty
- Amazon CloudWatch Events Critical No bounty
- Amazon CloudWatch Evidently Critical No bounty
- Amazon CloudWatch Internet Monitor Critical No bounty
- Amazon CloudWatch Logs Critical No bounty
- Amazon CloudWatch RUM Critical No bounty
- Amazon CodeCatalyst Critical No bounty
- Amazon CodeGuru Critical No bounty
- Amazon CodeGuru Profiler Critical No bounty
- Amazon CodeGuru Reviewer Critical No bounty
- Amazon CodeWhisperer Critical No bounty
- Amazon Cognito Critical No bounty
- Amazon Cognito Identity Critical No bounty
- Amazon Cognito Sync Critical No bounty
- Amazon Cognito User Pools Critical No bounty
- Amazon Comprehend Critical No bounty
- Amazon Comprehend Medical Critical No bounty
- Amazon Connect Critical No bounty
- Amazon Corretto Critical No bounty
- Amazon Data Firehose Critical No bounty
- Amazon Data Lifecycle Manager Critical No bounty
- Amazon Data Lifecycle Managers Critical No bounty
- Amazon DataZone Critical No bounty
- Amazon Detective Critical No bounty
- Amazon DevOps Guru Critical No bounty
- Amazon DevPay Critical No bounty
- Amazon DocumentDB Elastic Clusters Critical No bounty
- Amazon DocumentDB (with MongoDB compatibility) Critical No bounty
- Amazon DynamoDB Critical No bounty
- Amazon DynamoDB Accelerator (DAX) Critical No bounty
- Amazon DynamoDB Streams Critical No bounty
- Amazon EC2 Critical No bounty
- Amazon EC2 Auto Scaling Critical No bounty
- Amazon EC2 Image Builder Critical No bounty
- Amazon EC2 Instance Connect Critical No bounty
- Amazon EKS Auth Critical No bounty
- Amazon ElastiCache Critical No bounty
- Amazon ElastiCache Serverless Critical No bounty
- Amazon Elastic Block Store Critical No bounty
- Amazon Elastic Block Store (Amazon EBS) Critical No bounty
- Amazon Elastic Compute Cloud (Amazon EC2) Critical No bounty
- Amazon Elastic Container Registry Critical No bounty
- Amazon Elastic Container Registry (Amazon ECR) Critical No bounty
- Amazon Elastic Container Service Critical No bounty
- Amazon Elastic Container Service (Amazon ECS) Critical No bounty
- Amazon Elastic File System Critical No bounty
- Amazon Elastic File System (Amazon EFS) Critical No bounty
- Amazon Elastic Inference Critical No bounty
- Amazon Elastic Kubernetes Service Critical No bounty
- Amazon Elastic Kubernetes Service (Amazon EKS) Critical No bounty
- Amazon Elastic Transcoder Critical No bounty
- Amazon EMR Critical No bounty
- Amazon EMR Serverless Critical No bounty
- Amazon EventBridge Critical No bounty
- Amazon FinSpace Critical No bounty
- Amazon Forecast Critical No bounty
- Amazon Fraud Detector Critical No bounty
- Amazon FreeRTOS Critical No bounty
- Amazon FSx Critical No bounty
- Amazon FSx for Lustre Critical No bounty
- Amazon FSx for NetApp ONTAP Critical No bounty
- Amazon FSx for OpenZFS Critical No bounty
- Amazon FSx for Windows File Server Critical No bounty
- Amazon GameLift Critical No bounty
- Amazon GameSparks Critical No bounty
- Amazon GroundTruth Labeling Critical No bounty
- Amazon GuardDuty Critical No bounty
- Amazon GuardDuty ECS Runtime Monitoring Critical No bounty
- Amazon Honeycode Critical No bounty
- Amazon Inspector Critical No bounty
- Amazon Inspector Classic Critical No bounty
- Amazon Interactive Video Service Critical No bounty
- Amazon Interactive Video Service (Amazon IVS) Critical No bounty
- Amazon Interactive Video Service Chat Critical No bounty
- Amazon Kendra Critical No bounty
- Amazon Keyspaces (for Apache Cassandra) Critical No bounty
- Amazon Kinesis Critical No bounty
- Amazon Kinesis Data Streams Critical No bounty
- Amazon Kinesis Video Streams Critical No bounty
- Amazon Lex Critical No bounty
- Amazon Lightsail Critical No bounty
- Amazon Location Critical No bounty
- Amazon Location Service Critical No bounty
- Amazon lookout Critical No bounty
- Amazon Lookout for Equipment Critical No bounty
- Amazon Lookout for Metrics Critical No bounty
- Amazon Lookout for Vision Critical No bounty
- Amazon Lumberyard Critical No bounty
- Amazon Machine Learning Critical No bounty
- Amazon Machine Learning (Amazon ML) Critical No bounty
- Amazon Macie Critical No bounty
- Amazon Macie Classic Critical No bounty
- Amazon Managed Blockchain Critical No bounty
- Amazon Managed Blockchain (AMB) Critical No bounty
- Amazon Managed Grafana Critical No bounty
- Amazon Managed Service for Apache Flink Critical No bounty
- Amazon Managed Service for Prometheus Critical No bounty
- Amazon Managed Streaming for Apache Kafka Critical No bounty
- Amazon Managed Streaming for Apache Kafka (Amazon MSK) Critical No bounty
- Amazon Managed Streaming for Kafka Connect Critical No bounty
- Amazon Managed Workflows for Apache Airflow Critical No bounty
- Amazon Managed Workflows for Apache Airflow (Amazon MWAA) Critical No bounty
- Amazon Mechanical Turk Critical No bounty
- Amazon MemoryDB Critical No bounty
- Amazon Message Delivery Service Critical No bounty
- Amazon Message Gateway Service Critical No bounty
- Amazon Mobile Analytics Critical No bounty
- Amazon Monitron Critical No bounty
- Amazon MQ Critical No bounty
- Amazon Neptune Critical No bounty
- Amazon Neptune Analytics Critical No bounty
- Amazon Nimble Studio Critical No bounty
- Amazon Nova Critical No bounty
- Amazon One Enterprise Critical No bounty
- Amazon OpenSearch Critical No bounty
- Amazon OpenSearch Serverless Critical No bounty
- Amazon OpenSearch Service Critical No bounty
- Amazon Personalize Critical No bounty
- Amazon Pinpoint Critical No bounty
- Amazon Polly Critical No bounty
- Amazon Q Critical No bounty
- Amazon Q Business Critical No bounty
- Amazon Q Developer Critical No bounty
- Amazon Q Developer Agent Critical No bounty
- Amazon Q in Connect Critical No bounty
- Amazon Q in QuickSight Critical No bounty
- Amazon Q in Supply Chain Critical No bounty
- Amazon QLDB Critical No bounty
- Amazon Quantum Ledger Database (Amazon QLDB) Critical No bounty
- Amazon QuickSight Critical No bounty
- Amazon RDS Critical No bounty
- Amazon Redshift Critical No bounty
- Amazon Redshift Serverless Critical No bounty
- Amazon Rekognition Critical No bounty
- Amazon Relational Database Service (Amazon RDS) Critical No bounty
- Amazon Relational Database Service (Amazon RDS) for Db2 Critical No bounty
- Amazon Remote Configuration Critical No bounty
- Amazon Resource Group Tagging API Critical No bounty
- Amazon RHEL Knowledgebase Portal Critical No bounty
- Amazon Route 53 Critical No bounty
- Amazon Route 53 Application Recovery Controller Critical No bounty
- Amazon S3 Critical No bounty
- Amazon S3 Glacier Critical No bounty
- Amazon SageMaker Critical No bounty
- Amazon SageMaker Ground Truth Critical No bounty
- Amazon SageMaker HyperPod Critical No bounty
- Amazon Security Lake Critical No bounty
- Amazon SES Critical No bounty
- Amazon Silk Critical No bounty
- Amazon SimpleDB Critical No bounty
- Amazon Simple Email Service (Amazon SES) Critical No bounty
- Amazon Simple Email Service v2 Critical No bounty
- Amazon Simple Notification Service (Amazon SNS) Critical No bounty
- Amazon Simple Queue Service (Amazon SQS) Critical No bounty
- Amazon Simple Storage Service (Amazon S3) Critical No bounty
- Amazon Simple Workflow Service Critical No bounty
- Amazon Simple Workflow Service (Amazon SWF) Critical No bounty
- Amazon SNS Critical No bounty
- Amazon SQS Critical No bounty
- Amazon Sumerian Critical No bounty
- Amazon Textract Critical No bounty
- Amazon Timestream Critical No bounty
- Amazon Timestream for InfluxDB Critical No bounty
- Amazon Titan Critical No bounty
- Amazon Transcribe Critical No bounty
- Amazon Translate Critical No bounty
- Amazon Verified Permissions Critical No bounty
- Amazon Virtual Private Cloud (Amazon VPC) Critical No bounty
- Amazon VPC Critical No bounty
- Amazon WorkDocs Critical No bounty
- Amazon WorkLink Critical No bounty
- Amazon WorkMail Critical No bounty
- Amazon WorkSpaces Critical No bounty
- Amazon WorkSpaces Application Manager (Amazon WAM) Critical No bounty
- Amazon WorkSpaces Core Critical No bounty
- Amazon WorkSpaces Secure Browser Critical No bounty
- Amazon WorkSpaces Thin Client Critical No bounty
- Anything not in scope Critical No bounty
- Apache Kafka APIs for Amazon MSK clusters Critical No bounty
- api-user.e2ro.com/* Critical No bounty
- AWS Account Management Critical No bounty
- And 320 more on HackerOne.
Out of scope (1)
- https://*.amazonaws.com/*
Rules
What the policy asks of you, and the bug types it won't reward, quoted from AWS VDP (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
-
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
-
When conducting scanning campaigns targeting AWS resources, please consolidate all related findings into a single report.
-
You will provide us with a reasonable amount of time to resolve the issue before you disclose it publicly
-
You may only interact with accounts you own or with explicit written permission from AWS or the account owner
-
No stunt hacking
-
No extortion or harassment
Not accepted
-
Vulnerabilities only affecting users of unsupported or End-of-life browsers or operating systems
-
Broken link hijacking
-
Tabnabbing
-
Content spoofing and text injection issues
-
Attacks requiring physical access to a device (without prior written authorization)
-
Self-exploitation, such as self-XSS or self-DoS (unless it can be used to attack a different account)
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on forms with no sensitive actions (e.g., Logout)
-
Permissive CORS configurations without demonstrated security impact
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g., stack traces, application, or server errors)
-
Comma Separated Values (CSV) injection
-
Open redirects (unless you can demonstrate additional security impact)
-
SSL/TLS Configurations
-
Lack of SSL Pinning
-
Lack of jailbreak detection in mobile apps
-
Cookie handling (e.g., missing HttpOnly/Secure flags)
-
Content-Security-Policy configuration opinions
-
Optional email security features (e.g., SPF/DKIM/DMARC configurations)
-
Most issues related to rate limiting
-
Issues relating to excessive traffic/requests (e.g., DoS, DDoS)
-
Any other issues where testing may affect the availability of systems
-
Social engineering of AWS employees, contractors, vendors, or service providers. (e.g., phishing, opening support requests)
-
Attacks that are noisy to users or admins (e.g., spamming notifications or forms)
-
Physical attacks against AWS employees, offices, and data centers
-
Targeting assets of AWS customers or non-AWS sites hosted on our infrastructure
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 30 minutes ago.
-
Scope +
Added to scope: https://github.com/aws/s2n-quic
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
https://github.com/aws/s2n-quic
-
Scope added
https://github.com/deepjavalibrary/*
-
Scope added
https://github.com/strands-agents/*
-
Scope added
https://github.com/aws-actions/*
-
Scope added
https://github.com/awslabs/*
-
Scope added
AWS Organizations
-
Scope added
AWS Outposts
-
Scope added
AWS Panorama
-
Scope added
AWS Parallel Computing Service
-
Scope added
AWS ParallelCluster
-
Scope added
AWS Partner central account management
-
Scope added
AWS Partner Central Selling
-
Scope added
AWS Payment Cryptography
-
Scope added
AWS Payments
-
Scope added
AWS Performance Insights
-
Scope added
AWS Price List
-
Scope added
AWS Pricing Calculator
-
Scope added
AWS Private 5G
-
Scope added
AWS Private Certificate Authority
-
Scope added
AWS PrivateLink
-
Scope added
AWS Proton
-
Scope added
AWS Purchase Orders Console
-
Scope added
AWS re:Post Private
-
Scope added
AWS Recycle Bin
-
Scope added
AWS Redshift
-
Scope added
AWS Relational Database Service (RDS)
-
Scope added
AWS rePost Private
-
Scope added
AWS Resilience Hub
-
Scope added
AWS Resource Access Manager (AWS RAM)
-
Scope added
AWS Resource Access Manager (RAM)
-
Scope added
AWS Resource Explorer
-
Scope added
AWS Resource Groups
-
Scope added
AWS RoboMaker
-
Scope added
AWS Savings Plans
-
Scope added
AWS Schema Conversion Tool (AWS SCT)
-
Scope added
AWS SDK for .NET
-
Scope added
AWS SDK for .NET and Xamarin
-
Scope added
AWS SDK for C++
-
Scope added
AWS SDK for Go
-
Scope added
AWS SDK for Java
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-89332 | Inclusion of functionality from an untrusted control sphere in the Kiro Powers feature in Amazon Kiro IDE before version 0.8.135 might allow remote unauthenticated actors to obtain sensitive information from a developer workstation. Crafted repository content can cause the agent to modify the workspace settings file, which redirects the Kiro Powers registry request to an actor controlled endpoint | Medium 6.7 | 11 Sep 2026 |
| CVE-2026-18061 | Improper restriction of XML external entity references in the RemoteQueryCachePlugin in AWS Advanced JDBC Wrapper 3.3.0 through 4.2.0 might allow an actor with write access to the shared cache infrastructure to disclose sensitive files from application hosts that read cached query results, including stored database and IAM role credentials, via crafted XML data in a cached column value. To remedia | Medium 6.0 | 11 Sep 2026 |
| CVE-2026-81838 | A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgra | Medium 6.8 | 27 Aug 2026 |
| CVE-2026-77234 | Improper input validation in FreeRTOS-Kernel before 11.3.1 might allow an unprivileged task on MPU-enabled ports to execute code in privileged kernel context. To remediate this issue, users should upgrade to version 11.3.1 or later. | Critical 9.3 | 21 Aug 2026 |
| CVE-2026-77237 | Missing queue-set type validation in xQueueAddToSet() in the FreeRTOS-Kernel before 11.3.1 might allow an unprivileged task on MPU-enabled ports with configUSE_QUEUE_SETS=1 to read privileged kernel memory. To remediate this issue, users should upgrade to version 11.3.1 or later. | High 8.2 | 21 Aug 2026 |
| CVE-2026-77236 | Missing minimum size validation in secure context allocation in FreeRTOS-Kernel before 11.3.1 might allow local users to corrupt secure-world heap metadata via an out-of-bounds write with an undersized stack size parameter. To remediate this issue, users should upgrade to version 11.3.1 or later. | High 8.3 | 21 Aug 2026 |
| CVE-2026-77235 | Missing privilege verification in the secure context cleanup handler in FreeRTOS-Kernel before 11.3.1 might allow local users to cause a use-after-free condition in secure-world memory via the SVC handler for secure context deallocation. To remediate this issue, users should upgrade to version 11.3.1 or later. | High 8.3 | 21 Aug 2026 |
| CVE-2026-19643 | An out-of-bounds read issue in the Base64 decoder in Amazon aws-sdk-cpp before 1.11.862, on some platforms, might allow a remote authenticated user to crash an application that processes crafted Base64-encoded input. To remediate this issue, users should upgrade to version 1.11.862. | Medium 6.0 | 12 Aug 2026 |
| CVE-2026-19642 | An out-of-bounds write issue in the Base64 decoder in Amazon aws-sdk-cpp before 1.11.862 might allow a remote authenticated user to cause a crash or heap memory corruption in an application that processes crafted Base64-encoded input. To remediate this issue, users should upgrade to version 1.11.862. | Medium 6.0 | 12 Aug 2026 |
| CVE-2026-18953 | Improper limitation of a pathname to a restricted directory in the get_resource tool in Amazon awslabs.aws-transform-mcp-server 0.1.0 through 0.1.4 might allow a context-dependent actor to write arbitrary files outside the intended working directory via the savePath parameter. To remediate this issue, users should upgrade to version 0.1.5 or later. | Medium 6.3 | 5 Aug 2026 |
| CVE-2026-18954 | Incorrect authorization in the aggregation pipeline tool in Amazon AWS Labs DocumentDB MCP Server before 1.0.12 might allow an authenticated MCP client to perform inappropriate write operations on the connected database via write-capable aggregation pipeline stages that bypass the read-only mode enforcement logic. To remediate this issue, users should upgrade to version 1.0.12 or later. | Medium 5.7 | 5 Aug 2026 |
| CVE-2026-18657 | An uncontrolled search path element in Kiro CLI before version 2.10.0 on Windows might allow a remote unauthenticated actor to execute arbitrary code via a maliciously crafted project directory containing an executable that bypasses workspace trust protections when a local user starts Kiro CLI in the directory. To remediate this issue, users should upgrade to version 2.10.0 or higher. | High 8.5 | 4 Aug 2026 |
| CVE-2026-18656 | An uncontrolled search path element in Kiro IDE before version 1.0.228 on Windows might allow a remote unauthenticated actor to execute arbitrary code via a maliciously crafted project directory containing an executable that bypasses workspace trust protections when a local user opens the directory. To remediate this issue, users should upgrade to version 1.0.228 or higher. | High 8.5 | 4 Aug 2026 |
| CVE-2026-18654 | Key exchange without entity authentication in the EMR SSH helper commands in Amazon AWS CLI before 1.45.28 and AWS CLI v2 before 2.35.3 might allow man-in-the-middle attackers to intercept SSHsessions and file transfers via network positioning between the client and the EMR cluster endpoint. To remediate this issue, users should upgrade to AWS CLI v1 1.45.28 or later, or AWS CLI v2 2.35.3 or later | Medium 6.9 | 3 Aug 2026 |
| CVE-2026-18245 | Improper control of code generation in Amazon @aws-amplify/codegen-ui-react before 2.20.6 might allow a remote authenticated user to execute arbitrary code in end-user browsers, developer machines, CI/CD environments, and server-side rendering contexts via crafted Studio component or theme schema values due to insufficient coverage and effectiveness of the input validation introduced for CVE-2025- | Medium 6.4 | 30 Jul 2026 |
| CVE-2026-18140 | Uncontrolled recursion in the unknown-key skip path of the aws-smithy-json runtime crate before 0.62.7, which the smithy-rs code generator invokes from every generated struct deserializer, might allow remote unauthenticated users to cause a denial of service (process abort via stack exhaustion) via a single small HTTP request containing deeply nested JSON to a smithy-rs generated server. To remedi | High 8.7 | 30 Jul 2026 |
| CVE-2026-14265 | Deserialization of untrusted data in the RemoteQueryCachePlugin in Amazon Web Services AWS Advanced JDBC Wrapper 3.3.0 through 4.0.0 might allow an actor with write access to the shared cache infrastructure to execute arbitrary code on application servers that read cached query results via a crafted serialized Java object. The RemoteQueryCachePlugin uses ObjectInputStream without class filtering w | High 7.7 | 1 Jul 2026 |
| CVE-2026-13769 | Overly permissive file permissions in AWS CLI before 1.44.78 (v1) and 2.34.29 (v2) on Unix-like systems where the umask has not been configured to restrict file permissions (the default on most systems) may allow other local users on the same host to read credentials written by certain CLI subcommands (aws codeartifact login, aws iam create-virtual-mfa-device, aws deploy register). To remediate th | Medium 6.8 | 1 Jul 2026 |
| CVE-2026-13762 | Inconsistent interpretation of HTTP/2 requests in Amazon CloudFront with AWS WAF enabled might allow remote actors to bypass AWS WAF managed rule body inspection via crafted HTTP/2 requests that fragment the request body across frames so that only a partial body is inspected. This issue was remediated server-side. No customer action is required. | High 7.9 | 29 Jun 2026 |
| CVE-2026-13763 | Inconsistent interpretation of HTTP/2 requests in AWS Application Load Balancer with AWS WAF enabled might allow remote actors to bypass AWS WAF managed rule body inspection via crafted HTTP/2 requests that fragment the request body across frames so that only a partial body is inspected. This issue only impacts HTTP/2 ALB target groups. To remediate this issue, customers should enable the "Inspect | High 7.9 | 29 Jun 2026 |
| CVE-2026-10591 | Insufficient access control restrictions in the file write tool in Amazon Kiro IDE before version 0.11 might allow remote unauthenticated actors to execute arbitrary commands via crafted instructions that cause writes to execution-sensitive paths (such as .vscode/tasks.json), enabling auto-execution on folder open. To remediate this issue, users should upgrade to Kiro IDE version 0.11 or later. | High 8.6 | 2 Jun 2026 |
| CVE-2026-9255 | Missing input source validation in the tool authorization prompt in Kiro CLI before 1.28.0 allows a local attacker to execute arbitrary tools, including shell commands, without user approval by crafting content that is piped to kiro-cli via stdin. We recommend you to upgrade to kiro-cli version 1.28.0 or later. | High 8.4 | 22 May 2026 |
| CVE-2026-7461 | Improper neutralization of inputs used in an OS command in the FSx Windows File Server volume mounting component in Amazon ECS Agent on Windows before version 1.103.0 might allow a remote authenticated threat actor to execute shell commands with SYSTEM privileges on the underlying host via a specially crafted username field in an ECS task definition. This issue requires permissions to register ECS | High 7.5 | 30 Apr 2026 |
| CVE-2026-7426 | Insufficient validation of the prefix length field in IPv6 Router Advertisement processing in FreeRTOS-Plus-TCP before V4.2.6 and V4.4.1 allows an adjacent network actor to cause memory corruption by sending a crafted Router Advertisement with a prefix length value exceeding the maximum valid length, resulting in a heap buffer overflow. Users processing IPv4 RA only are not impacted. To mitigate t | Medium 6.1 | 29 Apr 2026 |
| CVE-2026-7425 | Insufficient option length validation in the IPv6 Router Advertisement parser in FreeRTOS-Plus-TCP before V4.2.6 and V4.4.1 allows an adjacent network actor to cause a denial of service (device crash) by sending a crafted Router Advertisement with a truncated PREFIX_INFORMATION option that is smaller than the expected structure size. To mitigate this issue, users should upgrade to the fixed versio | Medium 6.0 | 29 Apr 2026 |
| CVE-2026-7423 | Integer underflow in the ICMP and ICMPv6 echo reply handlers in FreeRTOS-Plus-TCP before V4.4.1 and V4.2.6 allows an adjacent network user to cause a denial of service (device crash) when outgoing ping support is enabled, because header sizes are subtracted from a packet length field without validating the field is large enough, resulting in a heap out-of-bounds read of up to approximately 65KB. T | Medium 6.0 | 29 Apr 2026 |
| CVE-2026-7424 | Integer underflow in the DHCPv6 sub-option parser in FreeRTOS-Plus-TCP before V4.4.1 and V4.2.6 allows an adjacent network actor to corrupt the device's IPv6 address assignment, DNS configuration, and lease times, and to cause a denial of service (permanent IP task freeze requiring hardware reset) by sending a single crafted DHCPv6 packet. The issue is present whenever DHCPv6 is enabled. To mitiga | High 7.2 | 29 Apr 2026 |
| CVE-2026-7422 | Insufficient packet validation in FreeRTOS-Plus-TCP before V4.2.6 and V4.4.1 allows an adjacent network actor to bypass all checksum and minimum-size validation by spoofing the Ethernet source MAC address to match one of the device's own registered endpoints, because the loopback detection mechanism skips all input validation for packets whose source MAC matches a local endpoint. To mitigate this | High 7.1 | 29 Apr 2026 |
| CVE-2026-6967 | Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users with delegated signing authority to bypass TUF specification integrity checks for delegated targets metadata and poison the local metadata cache, because load_delegations does not apply the same validation checks as the top-level targets metadata | High 7.1 | 24 Apr 2026 |
| CVE-2026-6966 | Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to bypass the TUF signature threshold requirement by duplicating a valid signature, causing the client to accept forged delegated role metadata. We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0. | High 7.0 | 24 Apr 2026 |
| CVE-2026-6968 | Incomplete path traversal fixes in awslabs/tough before tough-v0.22.0 allow remote authenticated users with delegated signing authority to write files outside intended output directories via absolute target names in copy_target/link_target, symlinked parent directories in save_target, or symlinked metadata filenames in SignedRole::write, because write paths trust the joined destination path withou | High 7.1 | 24 Apr 2026 |
| CVE-2026-31431 | In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy | High 7.8 | 22 Apr 2026 |
| CVE-2026-6437 | Improper neutralization of argument delimiters in the volume handling component in AWS EFS CSI Driver (aws-efs-csi-driver) before v3.0.1 allows remote authenticated users with PersistentVolume creation permissions to inject arbitrary mount options via comma injection. To remediate this issue, users should upgrade to version v3.0.1 | Medium 6.9 | 17 Apr 2026 |
| CVE-2026-5747 | An out-of-bounds write issue in the virtio PCI transport in Firecracker 1.13.0 through 1.14.3 and 1.15.0 on x86_64 and aarch64 might allow a local guest user with root privileges to crash the Firecracker VMM process or potentially execute arbitrary code on the host via modification of virtio queue configuration registers after device activation. Achieving code execution on the host requires additi | High 8.7 | 8 Apr 2026 |
| CVE-2026-5709 | Unsanitized input in the FileBrowser API in AWS Research and Engineering Studio (RES) version 2024.10 through 2025.12.01 might allow a remote authenticated actor to execute arbitrary commands on the cluster-manager EC2 instance via crafted input when using the FileBrowser functionality. To remediate this issue, users are advised to upgrade to RES version 2026.03 or apply the corresponding mitigati | High 7.7 | 6 Apr 2026 |
| CVE-2026-5708 | Unsanitized control of user-modifiable attributes in the session creation component in AWS Research and Engineering Studio (RES) prior to version 2026.03 could allow an authenticated remote user to escalate privileges, assume the virtual desktop host instance profile permissions, and interact with AWS resources and services via a crafted API request. To remediate this issue, users are advised to u | High 8.7 | 6 Apr 2026 |
| CVE-2026-5707 | Unsanitized input in an OS command in the virtual desktop session name handling in AWS Research and Engineering Studio (RES) version 2025.03 through 2025.12.01 might allow a remote authenticated actor to execute arbitrary commands as root on the virtual desktop host via a crafted session name. To remediate this issue, users are advised to upgrade to RES version 2026.03 or apply the corresponding m | High 8.7 | 6 Apr 2026 |
| CVE-2026-5485 | OS command injection in the browser-based authentication component in Amazon Athena ODBC driver before 2.0.5.1 on Linux might allow a threat actor to execute arbitrary code by using specially crafted connection parameters that are loaded by the driver during a local user-initiated connection. To remediate this issue, users should upgrade to version 2.0.5.1 or later. | High 7.3 | 3 Apr 2026 |
| CVE-2026-35558 | Improper neutralization of special elements in the authentication components in Amazon Athena ODBC driver before 2.1.0.0 might allow a threat actor to execute arbitrary code or redirect authentication flows by using specially crafted connection parameters that are processed by the driver during user-initiated authentication. To remediate this issue, users should upgrade to version 2.1.0.0. | High 7.3 | 3 Apr 2026 |
| CVE-2026-35562 | Allocation of resources without limits in the parsing components in Amazon Athena ODBC driver before 2.1.0.0 might allow a threat actor to cause a denial of service by delivering crafted input that triggers excessive resource consumption during the driver's parsing operations. To remediate this issue, users should upgrade to version 2.1.0.0. | High 8.7 | 3 Apr 2026 |
| CVE-2026-35561 | Insufficient authentication security controls in the browser-based authentication components in Amazon Athena ODBC driver before 2.1.0.0 might allow a threat actor to intercept or hijack authentication sessions due to insufficient protections in the browser-based authentication flows. To remediate this issue, users should upgrade to version 2.1.0.0. | Critical 9.1 | 3 Apr 2026 |
| CVE-2026-35560 | Improper certificate validation in the identity provider connection components in Amazon Athena ODBC driver before 2.1.0.0 might allow a man-in-the-middle threat actor to intercept authentication credentials due to insufficient default transport security when connecting to identity providers. This only applies to connections with external identity providers and does not apply to connections with A | Critical 9.1 | 3 Apr 2026 |
| CVE-2026-35559 | Out-of-bounds write in the query processing components in Amazon Athena ODBC driver before 2.1.0.0 might allow a threat actor to crash the driver by using specially crafted data that is processed by the driver during query operations. To remediate this issue, users should upgrade to version 2.1.0.0. | High 7.1 | 3 Apr 2026 |
| CVE-2026-4269 | A missing S3 ownership verification in the Bedrock AgentCore Starter Toolkit before version v0.1.13 may allow a remote actor to inject code during the build process, leading to code execution in the AgentCore Runtime. This issue only affects users of the Bedrock AgentCore Starter Toolkit before version v0.1.13 who build or have built the Toolkit after September 24, 2025. Any users on a version >=v | Medium 5.8 | 16 Mar 2026 |
| CVE-2026-4270 | Improper Protection of Alternate Path exists in the no-access and workdir feature of the AWS API MCP Server versions >= 0.2.14 and < 1.3.9 on all platforms may allow the bypass of intended file access restriction and expose arbitrary local file contents in the MCP client application context. To remediate this issue, users should upgrade to version 1.3.9. | Medium 6.8 | 16 Mar 2026 |
| CVE-2026-3494 | In MariaDB server version through 11.8.5, when server audit plugin is enabled with server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, if an authenticated database user invokes a SQL statement prefixed with double-hyphen (—) or hash (#) style comments, the statement is not logged. | Medium 5.3 | 3 Mar 2026 |
| CVE-2026-3338 | Improper signature validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0. | High 8.7 | 2 Mar 2026 |
| CVE-2026-3337 | Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis. The impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69 | High 8.2 | 2 Mar 2026 |
| CVE-2026-3336 | Improper certificate validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass certificate chain verification when processing PKCS7 objects with multiple signers, except the final signer. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0. | High 8.7 | 2 Mar 2026 |
| CVE-2026-1386 | A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should up | Medium 6.0 | 23 Jan 2026 |
| CVE-2026-0830 | Processing specially crafted workspace folder names could allow for arbitrary command injection in the Kiro GitLab Merge-Request helper in Kiro IDE before version 0.6.18 when opening maliciously crafted workspaces. To mitigate, users should update to the latest version. | High 8.4 | 9 Jan 2026 |
| CVE-2025-14503 | An overly-permissive IAM trust policy in the Harmonix on AWS framework may allow IAM principals in the same AWS account to escalate privileges via role assumption. The sample code for the EKS environment provisioning role is configured to trust the account root principal, which may enable any IAM principal in the same AWS account with sts:AssumeRole permissions to assume the role with administrati | High 8.6 | 15 Dec 2025 |
| CVE-2025-9624 | A vulnerability in OpenSearch allows attackers to cause Denial of Service (DoS) by submitting complex query_string inputs. This issue affects all OpenSearch versions between 3.0.0 and < 3.3.0 and OpenSearch < 2.19.4. | High 8.3 | 25 Nov 2025 |
| CVE-2025-62371 | OpenSearch Data Prepper as an open source data collector for observability data. In versions prior to 2.12.2, the OpenSearch sink and source plugins in Data Prepper trust all SSL certificates by default when no certificate path is provided. Prior to this fix, the OpenSearch sink and source plugins would automatically use a trust all SSL strategy when connecting to OpenSearch clusters if no certifi | High 7.4 | 15 Oct 2025 |
| CVE-2025-11616 | A missing validation check in FreeRTOS-Plus-TCP's ICMPv6 packet processing code can lead to an out-of-bounds read when receiving ICMPv6 packets of certain message types which are smaller than the expected size. These issues only affect applications using IPv6. Users should upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes. | Medium 5.3 | 10 Oct 2025 |
| CVE-2025-11618 | A missing validation check in FreeRTOS-Plus-TCP's UDP/IPv6 packet processing code can lead to an invalid pointer dereference when receiving a UDP/IPv6 packet with an incorrect IP version field in the packet header. This issue only affects applications using IPv6. We recommend upgrading to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes. | Medium 5.3 | 10 Oct 2025 |
| CVE-2025-11617 | A missing validation check in FreeRTOS-Plus-TCP's IPv6 packet processing code can lead to an out-of-bounds read when receiving a IPv6 packet with incorrect payload lengths in the packet header. This issue only affects applications using IPv6. We recommend users upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes. | Medium 5.3 | 10 Oct 2025 |
| CVE-2025-20286 | A vulnerability in Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI) cloud deployments of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to access sensitive data, execute limited administrative operations, modify system configurations, or disrupt services within the impacted systems. This vulnerability exists because credentials | Critical 9.9 | 4 Jun 2025 |
| CVE-2025-2887 | During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes. | Medium 5.7 | 27 Mar 2025 |
| CVE-2025-2888 | During a snapshot rollback, the client incorrectly caches the timestamp metadata. If the client checks the cache when attempting to perform the next update, the update timestamp validation will fail, preventing the next update until the cache is cleared. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes. | Medium 5.7 | 27 Mar 2025 |
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Amazon Web Services is committed to collaborating with the security community to identify and address vulnerabilities, ensuring the safety of our businesses and customers. We deeply value your contributions and take all security reports with utmost seriousness. If you would like to report a concern with Amazon Retail and Devices, please visit Amazon's Public Bug Bounty Program https://hackerone.com/amazonvrp.
This page outlines our practices for investigating and resolving potential vulnerabilities within our cloud services. Thank you for helping us maintain a secure environment.
What is AWS?
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.
Questions about getting started with AWS services? Connect with an expert »
Disclosure Policy
AWS requests that researcher's follow HackerOne's disclosure guidelines and once the report has been submitted, AWS will work to validate the reported vulnerability. If additional information is required to validate or reproduce the issue, AWS will work with you to obtain it. When the initial investigation is complete, results will be delivered to you along with a plan for resolution and discussion of public disclosure.
A few things to note about the AWS process:
-
Third-Party Products: Many vendors offer products within the AWS cloud. If the vulnerability is found to affect a third-party product, AWS will notify the owner of the affected technology. AWS will continue to coordinate between you and the third party. Your identity will not be disclosed to the third party without your permission.
-
Confirmation of Non-Vulnerabilities: If the issue cannot be validated, or is not found to originate in an AWS product, this will be shared with you.
-
Vulnerability Classification: AWS uses version 3.1 of the Common Vulnerability Scoring System (CVSS) to evaluate potential vulnerabilities. The resulting score helps quantify the severity of the issue and to prioritize our response. For more information on CVSS, please reference the NVD site.
Additional Program Policies
-
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged and we will request additional information.
-
Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
-
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
Submission Guidelines for Scanning Campaigns:
When conducting scanning campaigns targeting AWS resources, please consolidate all related findings into a single report. Submitting a high volume of individual reports for similar findings in quick succession can lead to a deduction in points. Repeated failure to follow this guideline can result in disqualification from the program.
AWS S3 related submissions:
AWS S3 related submissions to this program are limited to vulnerabilities specifically impacting the Amazon S3 service itself. Any other security concerns or issues related to the Amazon S3 service are out of the scope of the VDP and should be reported directly to the AWS security team at their dedicated inbox: [email protected]. Please ensure that all non-S3-related reports are directed accordingly.
Public Notification
If applicable, AWS will coordinate public notification of any validated vulnerability with you. Where possible, we prefer that our respective public disclosures be posted simultaneously.
In order to protect our customers, AWS requests that you not post or share any information about a potential vulnerability in any public setting until we have researched, responded to, and addressed the reported vulnerability, and informed customers if needed. Also, we respectfully ask that you do not post or share any data belonging to our customers. Addressing a valid reported vulnerability will take time, and the timeline will depend upon the severity of the vulnerability and the affected systems.
AWS makes public notifications in the form of Security Bulletins, which are posted in the AWS Security website. Individuals, companies, and security teams typically post their advisories on their own websites and in other forums and when relevant, we will include links to those third-party resources in AWS Security Bulletins.
Vulnerability Reporting Scope
When reporting potential vulnerabilities, please consider (1) realistic attack scenarios and (2) the security impact of the behavior. The following activities are out of scope for the AWS Vulnerability Reporting Program. Conducting any of the activities below will result in disqualification from the program permanently.
Core Ineligible Findings (but not limited to)
-
Theoretical vulnerabilities requiring unlikely user interaction or circumstances:
- Vulnerabilities only affecting users of unsupported or End-of-life browsers or operating systems.
- Broken link hijacking.
- Tabnabbing.
- Content spoofing and text injection issues.
- Attacks requiring physical access to a device (without prior written authorization).
- Self-exploitation, such as self-XSS or self-DoS (unless it can be used to attack a different account).
-
Theoretical vulnerabilities without real-world security impact:
- Clickjacking on pages with no sensitive actions.
- Cross-Site Request Forgery (CSRF) on forms with no sensitive actions (e.g., Logout).
- Permissive CORS configurations without demonstrated security impact.
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g., stack traces, application, or server errors).
- Comma Separated Values (CSV) injection.
- Open redirects (unless you can demonstrate additional security impact).
-
Optional security hardening steps / Missing best practices:
- SSL/TLS Configurations.
- Lack of SSL Pinning.
- Lack of jailbreak detection in mobile apps.
- Cookie handling (e.g., missing HttpOnly/Secure flags).
- Content-Security-Policy configuration opinions.
- Optional email security features (e.g., SPF/DKIM/DMARC configurations).
- Most issues related to rate limiting.
-
Vulnerabilities requiring hazardous testing (must not be attempted unless explicitly pre-authorized):
- Issues relating to excessive traffic/requests (e.g., DoS, DDoS).
- Any other issues where testing may affect the availability of systems.
- Social engineering of AWS employees, contractors, vendors, or service providers. (e.g., phishing, opening support requests).
- Attacks that are noisy to users or admins (e.g., spamming notifications or forms).
- Physical attacks against AWS employees, offices, and data centers.
- Targeting assets of AWS customers or non-AWS sites hosted on our infrastructure.
- Any vulnerability obtained through the compromise of AWS customer or employee accounts.
- Knowingly posting, transmitting, uploading, linking to, or sending malware.
- Pursuing vulnerabilities which send unsolicited bulk messages (spam).
Advisory Scope
This section defines the requirements necessary to issue a security advisory (e.g. CVE, GHSA).
In Scope for a CVE
The Amazon CNA will issue CVEs that support customers in addressing valid security vulnerabilities within the following classes:
- AWS Services delivered by AWS and publicly available to customers. (e.g. Amazon EC2, Amazon RDS).
- Amazon Services delivered by Amazon and publicly available to customers. (e.g. Amazon[.]com Seller API Service).
- Open-source software within a GitHub organization managed by Amazon or AWS.
- Client software published by Amazon or AWS and available for download from a website or download location owned and operated by us (e.g. Amazon Appstore SDK, Amazon Input SDK, Amazon Kindle App, Amazon MShop App, Amazon WorkSpaces client).
- Devices manufactured by Amazon or AWS and available to customers for purchase and use (e.g. Amazon Fire TV, Amazon Echo devices, Amazon Kindle, AWS Outpost).
Additionally, all of the requirements below must be met:
- Customer Impacting: The issue must exist within an Amazon or AWS-owned class which is publicly available to customers; AND
- Customer Agency: Remediation of supported or EOL/EOS product issues requires customer action, including making a risk-based decision on handling the remediation (OR customers need to assess possible impact) OR when a valid security vulnerability will become public (OR has the potential of becoming public); AND
- CVSS score: 4.0 (MEDIUM) or higher.
Out of Scope for a CVE
Services, software, or hardware issues that are deemed not a vulnerability include but are not limited to:
- Non-default configuration or changes made using valid credentials that were correctly authorized
- Targeting assets of Amazon or AWS customers (or non-AWS sites hosted on AWS infrastructure)
- Any vulnerability obtained through the compromise of Amazon or AWS customer or employee accounts
- Any Denial of Service (DoS) attack against Amazon or AWS products (or Amazon or AWS customers)
- Physical attacks against Amazon or AWS employees, offices, and data centers
- Social engineering of Amazon or AWS employees, contractors, vendors, or service providers
- Knowingly posting, transmitting, uploading, linking to, or sending malware
- Pursuing vulnerabilities which send unsolicited bulk messages (spam)
Good Faith Security Research
All vulnerability research must be conducted in good faith. This means:
- You will follow this policy, and any other relevant agreements you have with us
- Your research must consist exclusively of good faith testing, investigation, or correction of a security flaw, with the primary goal of promoting the safety of the class of devices, machines, or online services to which any accessed computers belong
- You will not violate AWS customers’ security and privacy, and will not harm individuals or the public
- Your research will proceed only as far as necessary to demonstrate or clarify the security issue, and no further
- If a vulnerability provides unintended access to data, you will limit the amount of data you access to the minimum required for effectively demonstrating a proof of concept. Stop the research and submit a report immediately if you encounter any user data during testing, such as personal information, financial information, or proprietary information
- You will report the findings of your research to us within 72 hours of determining a potential security concern via our Vulnerability Disclosure Program on HackerOne (https://hackerone.com/aws_vdp) or by emailing [email protected] [(PGP Key)] 20.
- You will provide us with a reasonable amount of time to resolve the issue before you disclose it publicly
- You may only interact with accounts you own or with explicit written permission from AWS or the account owner
- No stunt hacking
- No extortion or harassment
Safe Harbor
We consider Good Faith Security Research to be authorized activity that is protected from adversarial legal action by us. This means that, for activity conducted while this program is active, we:
- Will not bring legal action against you or report you for Good Faith Security Research, including for bypassing technological measures we use to protect the applications in scope; and,
- Will take steps to make known that you conducted Good Faith Security Research if someone else brings legal action against you.
Note that for the purposes of safe harbor, AWS does NOT waive a right to pursue remedies against security research activities targeting other AWS customers’ resources, operations, or end users, including but not limited to:
- unauthorized cross-customer environment access
- manipulation, monitoring/collection
- spoofing
- social engineering, including but not limited to phishing
- impersonating AWS, AWS employees, AWS services, or AWS products
- impersonating AWS or customer marketplace offerings (eg. AMIs, container images, templates, models, etc)
- impersonating any other company, their employees, services, products or offerings
- provisioning resources to mimic AWS infrastructure or AWS customer resources
- Denial of Service, Distributed Denial of Service, simulated DoS, simulated DDoS
- port, protocol, or request flooding
- any type of brute forcing
- IP or Resource cycling/churning
- DNS hijacking, Pharming, or zone walking via Amazon Route 53
- stunt hacking
An explicit authorization or permission granted by any single AWS customer for the purposes of their continuous vulnerability scanning, penetration testing, security configuration validation, or vulnerability rewards program (VRP) cannot exceed the bounds of the specific customers’ accounts and resources and does NOT grant authorization for abusive activities via any AWS service.
Individuals or companies conducting security research are strongly encouraged to contact AWS Security (via HackerOne (https://hackerone.com/aws_vdp) or by emailing [email protected] [(PGP Key)] 20) to review their planned methodology and seek guidance or operational support prior to any activities. Security research that is not conducted in good faith may subject your AWS account(s) to active response measures, such as offending resource isolation, account suspension, resource / account termination, legal remedies, or relevant law enforcement referral.
Keep in mind that we are not able to authorize security research on third-party infrastructure, and a third party is not bound by this safe harbor statement.
Engagement SLA
AWS is committed to being responsive and keeping you informed of our progress. You will receive a non-automated response confirming receipt of your initial report within 24 hours, timely updates, and monthly check-ins throughout the engagement. You may request updates at any time, and we welcome dialogue that clarifies any concern or disclosure coordination.
Program Eligibility and Compliance
At AWS, we’re committed to maintaining a secure and compliant Vulnerability Disclosure Program while adhering to global regulations. Please review these important guidelines:
Eligibility Requirements:
- Participation is subject to compliance with applicable sanctions and trade regulations in conformity with the AWS Customer Agreement https://aws.amazon.com/agreement/#:~:text=11.6%20Trade%20Compliance,applicable%20government%20authority .
- Non-monetary Rewards such as merch store credits and physical swag cannot be issued to individuals in sanctioned countries/regions.
- Participants are responsible for compliance with local tax laws and regulations.