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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-10177 is a server-side request forgery issue reported in Aider-AI Aider 0.86.3. A remote authenticated attacker may be able to make the application fetch unintended internal resources, including AWS EC2 metadata. Public disclosure is reported, but active exploitation is not confirmed by KEV or the provided sources.
Executive priority
Treat this as a moderate cloud-exposure risk. It is most urgent for hosted Aider deployments on AWS or systems with sensitive internal network access. Local-only developer installations are lower priority, but should still be tracked for update.
Technical view
The reported flaw affects requests.get usage in api_docs.py, tied to AWS EC2 metadata endpoint access. It is classified as CWE-918 SSRF with CVSS 2.0 score 6.5 and authentication required. Sources say a patch pull request exists but awaits acceptance, so a confirmed fixed release is not established here.
Likely exposure
Exposure is most relevant where Aider 0.86.3 runs in environments that can reach internal services or EC2 metadata endpoints, especially with privileged cloud credentials. Internet-facing or multi-user deployments are higher concern than isolated local developer use.
Exploitation context
The source bundle says an exploit has been publicly disclosed and may be used. KEV is false, and no cited source confirms active exploitation in the wild. The CVSS vector indicates proof-of-concept maturity and a single authentication requirement.
Researcher notes
Evidence is limited to the CVE/VulDB record and linked GitHub tracking. The affected version is listed as 0.86.3. The bundle names requests.get in api_docs.py and AWS metadata access, but does not provide maintainer-confirmed fixed release details.
Mitigation direction
Inventory and prioritize any Aider 0.86.3 deployments.
Monitor the upstream issue and PR for an accepted fix or release.
Avoid running affected instances with unnecessary EC2 metadata access.
Restrict instance metadata and cloud IAM permissions to least privilege.
Check vendor guidance before assuming a patch version exists.
Validation and detection
Confirm whether Aider 0.86.3 is present in workstations, containers, or servers.
Identify deployments running on AWS EC2 or networks with internal metadata access.
Review whether api_docs.py behavior is reachable by authenticated remote users.
Track GitHub issue 5075 and PR 5137 for maintainer resolution.
After updating, verify the deployed version includes the accepted fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
0ADP providers
8Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.