A security flaw has been discovered in Aider-AI Aider 0.86.3. Affected by this vulnerability is the function editor_coder.run of the file auth.py of the component Architect Mode. Performing a manipulation results in code injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
Security readout for executives and security teams
Plain-English summary
Aider 0.86.3 has a reported code injection flaw in Architect Mode. An authenticated remote attacker could manipulate behavior so code runs through auth.py's editor_coder.run path. Public exploit material is reported, but the bundle does not show confirmed real-world exploitation or a vendor fix.
Executive priority
Treat this as a near-term engineering risk for teams using Aider 0.86.3. The business urgency is moderate because exploit material is public, but confirmed active exploitation and vendor remediation are not shown in the provided evidence.
Technical view
The report maps to CWE-74/CWE-94 and CVSS 2.0 score 6.5 with network access, low complexity, and single authentication required. The affected component is Architect Mode, specifically editor_coder.run in auth.py. Sources state remote exploitation is possible and exploit material is public.
Likely exposure
Exposure appears limited to organizations running Aider 0.86.3, especially where Architect Mode is reachable by authenticated users or automation handling untrusted input. The sources do not identify other affected versions or hosted service exposure.
Exploitation context
VulDB reports a public exploit and remote exploitability, but KEV is false and the provided sources do not confirm active exploitation. Authentication is required according to the CVSS vector and CTI reference tags.
Researcher notes
Evidence is concentrated in VulDB and a GitHub issue reference. The record names Aider 0.86.3 only. Avoid expanding scope to other versions without vendor confirmation. Prioritize validating authenticated remote reachability, Architect Mode usage, and whether untrusted content can influence the affected path.
Mitigation direction
Inventory Aider installations and identify any version 0.86.3 deployments.
Restrict Architect Mode to trusted users and trusted project inputs only.
Run Aider in least-privilege, isolated environments until guidance is available.
Monitor Aider issue 5058 and vendor channels for a fixed release or workaround.
Review VulDB updates before assuming any patch or mitigation exists.
Validation and detection
Check package manifests, containers, and developer workstations for Aider 0.86.3.
Confirm whether Architect Mode is enabled or used in automated workflows.
Review access controls for any remotely reachable Aider usage.
Look for local references to auth.py and editor_coder.run in deployed copies.
Document whether remediation depends on unavailable vendor guidance.
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 · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
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-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.