CVE-2026-77810: Code Injection via Gremlin Query Passthrough in Amazon Athena Neptune Connector
In the Neptune connector, a user with access to Neptune through Athena Federated Query could gain access to properties in the Lambda supplying the compute for the connector. To remediate this issue, users should upgrade to aws-athena-query-federation v2026.30.1 or later.
Security readout for executives and security teams
Plain-English summary
An authenticated user able to reach Amazon Neptune through Athena Federated Query could inject code through the connector and access properties of its supporting Lambda. Because compromise may cross security boundaries and affect confidentiality, integrity, and availability, exposed deployments require urgent remediation.
Executive priority
Remediate immediately where version 2024.15.1 is deployed and users can access Neptune through Athena. The 9.9 rating and potential Lambda-context access justify emergency prioritization, although the supplied evidence does not show active exploitation.
Technical view
CVE-2026-77810 is a CWE-95 code-injection flaw in Gremlin query passthrough within the Amazon Athena Neptune connector. The supplied record identifies version 2024.15.1 and assigns CVSS 3.1 score 9.9: network-accessible, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure requires the affected Athena Federated Query Neptune connector and a user with Neptune access through Athena. The supplied bundle specifically identifies version 2024.15.1; it does not establish that other versions are affected. Confirm deployed connector versions and relevant user access.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as CISA KEV. Exploitation nevertheless requires only low privileges according to the CVSS vector. Treat authorized query users as potentially capable of crossing into the connector Lambda's security context.
Researcher notes
The record describes Gremlin query passthrough leading to code injection and Lambda property access, but provides no payload mechanics or confirmed exploitation evidence. Scope conclusions should remain limited to the identified connector version and access path. Validate versioning and permissions defensively; avoid testing against production with offensive techniques.
Mitigation direction
Upgrade aws-athena-query-federation to version 2026.30.1 or later.
Prioritize connector instances accessible to multiple or less-trusted Athena users.
Consult the AWS bulletin and GitHub advisory for current vendor guidance.
Apply normal change controls and preserve relevant logs before remediation.
Validation and detection
Inventory deployed Athena Neptune connector versions and identify version 2024.15.1.
Confirm upgraded deployments report aws-athena-query-federation version 2026.30.1 or later.
Review which identities can query Neptune through Athena Federated Query.
Review available connector and Lambda telemetry for unexpected access or behavior.
Verify connector functionality after upgrading without performing exploit testing.
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-95: Code execution behavior lookup
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.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-95 · source CWE mapping
Improper Neutralization of Directives in Dynamically Evaluated Code
Improper Neutralization of Directives in Dynamically Evaluated Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.