LiveActive security incident?Get immediate response
CVE Record

CVE-2026-85663: Aim 3.29.1 Remote Code Execution via Unauthenticated Method Dispatch

Aim 3.29.1 remote tracking server fails to authenticate requests and dispatches arbitrary methods through getattr without allowlist validation. Unauthenticated attackers can register clients, instantiate Repo resources, and invoke arbitrary methods to read experiments or delete runs.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Aim 3.29.1’s remote tracking server reportedly accepts unauthenticated requests and lets callers invoke server-side methods without an approved-method list. This could expose experiment data or allow runs to be deleted. Although described as remote code execution, the supplied evidence does not detail the code-execution mechanism.

Executive priority

Treat reachable Aim 3.29.1 tracking servers as an immediate containment priority because unauthenticated access may compromise experiments and disrupt operations. Determine exposure now, restrict access, preserve data, and follow vendor remediation guidance. Do not assume versions other than 3.29.1 are affected without confirmation.

Technical view

The tracking service reportedly lacks request authentication and dynamically resolves attacker-selected methods using getattr without allowlist validation. An unauthenticated network attacker may register clients, instantiate Repo resources, and invoke methods affecting confidentiality, integrity, and availability. The bundle assigns CVSS 3.1 score 9.8 and CWE-306.

Likely exposure

Highest risk applies to reachable Aim 3.29.1 remote tracking servers, especially those exposed to untrusted networks. The supplied structured version metadata is ambiguous, listing version “0” with a default unaffected status; therefore, affected versions beyond the specifically named 3.29.1 cannot be established.

Exploitation context

No CISA KEV listing or other evidence of active exploitation is provided. Exploitation is described as network-accessible, unauthenticated, low-complexity, and requiring no user interaction. Public technical references identify the vulnerable dispatch path, but this bundle does not establish observed attacks or provide a confirmed exploitation timeline.

Researcher notes

The central weakness is missing authentication combined with unrestricted dynamic method dispatch. The supplied description supports unauthorized experiment reading and run deletion. The advisory title claims remote code execution, but the bundle does not explain the code-execution primitive. Version-range data is internally unclear, so testing and scoping should remain conservative.

Mitigation direction

  • Restrict the Aim tracking service to trusted networks and authenticated access paths immediately.
  • Remove direct internet exposure using firewall, private-network, or access-proxy controls.
  • Check Aim’s issue tracker and vendor guidance for a fixed release or approved mitigation.
  • Preserve backups of experiment data and verify recovery procedures before remediation.
  • Disable the affected tracking service if exposure cannot be adequately restricted.

Validation and detection

  • Inventory Aim deployments and confirm exact installed versions, prioritizing version 3.29.1.
  • Identify whether tracking-server ports are reachable from internet or other untrusted networks.
  • Review service configuration and access controls for enforced authentication before request dispatch.
  • Examine logs for unknown client registrations, unusual method requests, data access, or run deletion.
  • After remediation, verify unauthenticated requests cannot create resources or invoke repository methods.
Prepared
Confidence
medium
Sources
6

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-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-85663 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

2 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-85663Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
aimhubioaim0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.