CVE-2026-10177 in Aider
Summary
by MITRE • 05/31/2026
A security vulnerability has been detected in Aider-AI Aider 0.86.3. This affects the function requests.get of the file api_docs.py of the component AWS EC2 Metadata Endpoint. The manipulation leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. It is suggested to install a patch to address this issue. The pull request to fix this issue awaits acceptance.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 06/23/2026
The security vulnerability identified in Aider-AI Aider 0.86.3 represents a critical server-side request forgery flaw that emerges from improper handling of HTTP requests within the AWS EC2 Metadata Endpoint component. This vulnerability specifically targets the requests.get function implementation in the api_docs.py file, creating an attack vector where malicious actors can manipulate the application's behavior to make unauthorized requests to internal or external systems. The flaw stems from insufficient validation and sanitization of input parameters that are passed to the HTTP request mechanism, allowing attackers to potentially bypass security controls and access restricted resources.
The technical implementation of this vulnerability enables remote exploitation through manipulation of the function parameters that govern how requests are constructed and executed. When the application processes user-supplied data through the requests.get method without proper validation, it creates opportunities for attackers to inject malicious endpoints or modify request targets. This type of vulnerability falls under CWE-918, which specifically addresses server-side request forgery conditions where applications fail to properly validate and sanitize external input before using it in HTTP requests. The attack surface is particularly concerning because the AWS EC2 Metadata Endpoint serves as a privileged interface that typically provides sensitive system information and credentials.
The operational impact of this vulnerability extends beyond simple data exfiltration, as attackers could potentially gain unauthorized access to cloud resources, extract metadata containing sensitive credentials, or even escalate privileges within the affected environment. The remote exploit capability means that attackers do not require physical access or network proximity to the target system, making this vulnerability particularly dangerous in cloud environments where applications may be exposed to public internet traffic. This flaw can enable lateral movement within networks and potentially allow attackers to establish persistent access through credential theft from metadata endpoints.
Security professionals should immediately implement mitigations including input validation, parameter sanitization, and strict endpoint whitelisting for all external request operations. The recommended approach involves updating the application code to validate all inputs before passing them to HTTP request functions and implementing proper authorization controls for accessing metadata endpoints. Organizations should also consider network segmentation and firewall rules to limit access to internal metadata services, while monitoring for suspicious request patterns that might indicate exploitation attempts. The vulnerability demonstrates the importance of following secure coding practices such as those outlined in the OWASP Top Ten and MITRE ATT&CK framework, particularly focusing on prevention of server-side request forgery through proper input validation and access control mechanisms. Additionally, implementing automated security scanning tools can help detect similar vulnerabilities in other components that may utilize similar HTTP request patterns, ensuring comprehensive protection against this class of attack vectors.