VulnerabilityPublished 18 Nov 2025

CVE-2025-63604: mcp-server-aws-resources-python · CVE-2025-63604 is a code injection

Affects mcp-server-aws-resources-pythonSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPImcp-server-aws-resources-python`pkg:pypi/mcp-server-aws-resources-python`Other threats	Affected =0.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-63604, organizations should immediately audit their use of the baryhuang/mcp-server-aws-resources-python package and avoid using version 0.1.0 until a patched version is available. Developers must remove or restrict access to dangerous Python built-ins (__import__, getattr, hasattr) from execution namespaces to prevent abuse. Avoid using exec() on untrusted user input; instead, implement safer query parsing and execution methods that do not rely on dynamic code execution. Employ strict input validation and sanitization to neutralize potentially malicious payloads. Implement sandboxing or restricted execution environments to limit the scope of code execution and prevent access to sensitive environment variables and file systems. Rotate AWS credentials immediately if compromise is suspected and enforce least privilege principles on AWS IAM roles to minimize damage. Monitor logs for unusual query patterns or execution attempts indicative of exploitation. Additionally, adopt runtime application self-protection (RASP) and intrusion detection systems tailored for cloud environments to detect and block exploitation attempts. Finally, maintain up-to-date inventory of third-party packages and apply security patches promptly once available.

Description

CVE-2025-63604 is a code injection vulnerability in baryhuang/mcp-server-aws-resources-python 0.1.0 that enables remote code execution via the execute_query method due to insufficient input validation. The vulnerability arises from exposing dangerous Python built-ins (__import__, getattr, hasattr) and using exec() on user-supplied input. Exploitation can lead to theft of AWS credentials, unauthorized file system and environment access, and full system compromise. No authentication or user interaction is required, and the attack can be performed remotely over the network. The CVSS score is 6.5 (medium severity), reflecting the ease of exploitation but limited impact on availability. European organizations using this package to manage AWS resources are at risk, especially those with critical cloud infrastructure. Mitigation requires removing dangerous built-ins from execution contexts, avoiding exec() on untrusted input, and implementing strict input validation and sandboxing.

Impact

For European organizations, the impact of CVE-2025-63604 can be substantial, especially for those heavily reliant on AWS cloud services and using the affected package for resource management. Successful exploitation can lead to theft of AWS credentials, enabling attackers to access, modify, or delete cloud resources, potentially causing data breaches, service disruptions, and financial losses. Confidentiality is primarily at risk due to credential exposure and environment variable disclosure. Integrity is also threatened as attackers can execute arbitrary code and manipulate system or cloud resources. Although availability impact is rated low, indirect effects such as resource misuse or deletion can cause operational downtime. Organizations in sectors with stringent data protection regulations (e.g., GDPR) may face compliance violations and reputational damage if breaches occur. The vulnerability's ease of exploitation without authentication or user interaction increases the risk of automated attacks and widespread exploitation if left unmitigated. European cloud service providers and enterprises with critical infrastructure hosted on AWS are particularly vulnerable, necessitating urgent remediation to prevent potential large-scale compromises.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/baryhuang/mcp-server-aws-resources-python/issues/8 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Nov 2025, 17:17 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats