A weakness has been identified in Aider-AI Aider 0.86.3. Affected by this issue is some unknown functionality of the component Code Generation Workflow. Executing a manipulation can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could 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-AI Aider 0.86.3 is reported to have a SQL injection weakness in its code generation workflow. The issue is remotely reachable, requires authentication per the CVSS vector, and has a public proof of concept. No confirmed active exploitation or vendor fix is shown in the bundle.
Executive priority
Treat this as a moderate-priority exposure review, not an emergency internet-wide incident. Public exploit availability raises urgency, but authentication is required and no active exploitation is confirmed. Prioritize teams using Aider 0.86.3 in shared, automated, or externally reachable workflows.
Technical view
The reported flaw is CWE-89/CWE-74 in an unspecified Code Generation Workflow function of Aider 0.86.3. VulDB rates it CVSS 6.5 with network access, low complexity, authenticated access, and partial confidentiality, integrity, and availability impact. The vulnerable code path and patch status are not defined in the provided sources.
Likely exposure
Exposure is most likely where Aider 0.86.3 is installed and its code generation workflow is reachable by authenticated remote users or automation. The bundle does not identify a specific endpoint, deployment model, or database path, so teams must confirm local usage.
Exploitation context
The bundle says an exploit is publicly available and could be used, but KEV is false and no cited source confirms active exploitation. The CVSS vector indicates authentication is required, lowering broad internet risk while still mattering for shared or semi-trusted environments.
Researcher notes
Evidence is thin: the affected function is unknown, the report says SQL injection, and the submit title mentions code injection. No patch, commit, or vendor acknowledgement is included. Validation should focus on version presence, reachable workflow paths, and any downstream datastore impact.
Mitigation direction
Inventory Aider deployments and flag version 0.86.3 for review.
Restrict access to Aider workflows to trusted authenticated users only.
Avoid exposing affected workflows to untrusted remote inputs.
Monitor Aider-AI issue 5077 and VulDB for vendor guidance.
Apply a vendor patch or workaround when published.
Use least-privilege database access for any connected datastore.
Validation and detection
Confirm installed Aider versions in developer and automation environments.
Identify whether the Code Generation Workflow is enabled or remotely reachable.
Review access controls for users or systems invoking Aider workflows.
Check logs for unusual SQL errors or unexpected data changes.
Track the referenced GitHub issue for maintainer response.
Do not test public proof-of-concept material in production.
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.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 database injection or access, so collection and exfiltration 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.
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.