CVE-2026-10274 in aem-mcp-server
Summary
by MITRE • 06/01/2026
A vulnerability was determined in indrasishbanerjee aem-mcp-server up to b5f833aef9b5dfd17a5991b3b18a8a11edbdc583. This impacts the function getAssetMetadata of the file src/mcp-server.ts of the component Axios Request Flow. Executing a manipulation of the argument assetPath can lead to server-side request forgery. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 06/01/2026
The vulnerability identified in the indrasishbanerjee aem-mcp-server repository represents a critical server-side request forgery flaw within the Axios Request Flow component. This security weakness resides in the getAssetMetadata function located in the src/mcp-server.ts file, where improper input validation allows attackers to manipulate the assetPath argument. The absence of version control in this project creates significant challenges for determining which specific releases are affected, as the vulnerability exists in code up to commit b5f833aef9b5dfd17a5991b3b18a8a11edbdc583. The flaw enables remote exploitation through manipulation of the assetPath parameter, potentially allowing attackers to make unauthorized requests to internal systems that the server can access.
The technical implementation of this vulnerability stems from insufficient sanitization of user-provided input within the asset path handling mechanism. When the getAssetMetadata function processes the assetPath argument, it fails to properly validate or sanitize the input before using it in subsequent HTTP requests through the Axios library. This creates an environment where an attacker can inject malicious URLs or network paths that the server will attempt to access on behalf of the user. The vulnerability specifically aligns with CWE-918, which describes server-side request forgery vulnerabilities where applications fail to properly validate and sanitize user-supplied URLs or network paths. The attack vector is remote, meaning that malicious actors can exploit this flaw from outside the network boundary without requiring physical access or authentication to the system.
The operational impact of this vulnerability extends beyond simple data exfiltration, as it could enable attackers to perform reconnaissance on internal network resources that the server has access to. This includes potentially accessing internal APIs, databases, or other services that are not directly exposed to the internet but are reachable from the server hosting the vulnerable application. The public disclosure of this exploit increases the risk profile significantly, as it provides threat actors with a known method for compromising systems. The lack of response from the project maintainers after being informed through an issue report creates additional risk, as the vulnerability remains unpatched and potentially exploitable in production environments. This scenario demonstrates the importance of proper input validation and the principle of least privilege in API design, where external inputs should never be blindly trusted or passed directly to network requests.
The mitigation strategies for this vulnerability should focus on implementing robust input validation and sanitization mechanisms within the asset path handling code. All user-provided inputs should be validated against a strict whitelist of acceptable characters and patterns before being processed. The implementation should include proper URL encoding and validation to prevent malicious URL injection attacks. Additionally, the system should implement network-level restrictions to prevent the server from making unauthorized requests to internal resources, using techniques such as network segmentation and firewall rules. Organizations should also consider implementing monitoring and logging for unusual network requests originating from the server, which could indicate exploitation attempts. The vulnerability highlights the necessity of following secure coding practices and the ATT&CK framework's emphasis on preventing command injection and server-side request forgery attacks through proper input validation and network segmentation measures.