# CVE-2026-110812: Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune

> Authenticated attackers can execute arbitrary code and access internal credentials via deserialization in the Gremlin import path.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-6rrf-xw64-h782

## What is CVE-2026-110812?

CVE-2026-110812 is a critical unsafe deserialization vulnerability in AWS Amazon Neptune Engine, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Deserialization of untrusted data in the Gremlin graph data import component in Amazon Neptune engine might allow an authenticated remote actor with standard database permissions to execute arbitrary code and access internal service credentials.

To remediate this issue, users not enrolled in auto-update should upgrade to Amazon Neptune engine version 1.5.0.0.(Backports to 1.4.8.1 and 1.4.7.1)

Weakness: CWE-918 (Server-Side Request Forgery), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-110812?


## How do I fix CVE-2026-110812?

No fix has been published for CVE-2026-110812 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110812 being exploited?

There is no known exploitation of CVE-2026-110812 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110812 and fix it if it is affected.

What it is: CVE-2026-110812 is a critical unsafe deserialization vulnerability in AWS Amazon Neptune Engine, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110812 in the wild and no public exploit code.

Affected product: AWS Amazon Neptune Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110812/ (Markdown: https://insights.sbomify.com/CVE-2026-110812/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110812
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110812
- OSV: https://osv.dev/vulnerability/CVE-2026-110812

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110812/
Summaries are generated and may contain mistakes; the official description above is the record.