// Security Advisory Triage
Neptune deserialization flaw lets authenticated users trigger unsafe query processing
AWS security bulletins · published 2026-10-15 17:05 UTC
CORRECTED 2026-10-18 23:27 UTC — [CORRECTION · WHY IT MATTERS] Original: “This is a managed service vulnerability you cannot patch yourself — AWS must upgrade the engine.” Fact: The bulletin says the issue is fixed in Neptune engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0; clusters with auto minor version upgrade enabled get it in the next maintenance window, and customers who manage engine versions manually should upgrade. / Checked against AWS Security Bulletin 2026-136-AWS on 2026-10-18.
Stood 78h 22m · cause writer overreach · every correction ↗
WHAT CHANGEDAWS disclosed CVE-2026-110812 on 15 October 2026, a deserialization vulnerability in Apache TinkerPop's Gremlin functionality used by Amazon Neptune. All Neptune engine versions >=1.2.0.0 are affected. An authenticated principal with Neptune data-plane query permissions can submit requests that cause the query engine to process untrusted input unsafely, potentially leading to unintended activity within the query engine environment.
WHY IT MATTERSAWS has fixed this in Neptune engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0. Clusters with auto minor version upgrade enabled get the fix in their next maintenance window; if you manage engine versions manually, you must upgrade the cluster yourself. An attacker who already has Neptune query permissions could cause the query engine to process untrusted input unsafely. The broad version range (1.2.0.0 and later) means most production Neptune clusters are affected.
WHAT TO DOCheck your Neptune cluster engine versions in the AWS console. If running 1.2.0.0 or later, upgrade to the patched version for your engine line (1.4.7.1, 1.4.8.1 or 1.5.0.0), or confirm auto minor version upgrade is enabled and the fix lands in your next maintenance window. Until then, review IAM policies so only trusted principals have neptune-db data-plane (query) permissions, since exploitation requires authenticated query access.
Original text (as first published, superseded)
WHY IT MATTERSThis is a managed service vulnerability you cannot patch yourself — AWS must upgrade the engine. An attacker who already has Neptune query permissions can exploit this to execute unintended operations in the query engine environment, which in a managed service context means activity outside your direct control. The broad version range means most production Neptune clusters are affected.
WHAT TO DOCheck your Neptune cluster engine versions in the AWS console. If running >=1.2.0.0, schedule an upgrade to the patched engine version listed in the full bulletin. Review IAM policies to confirm only necessary principals have neptune-db:* data-plane permissions, since exploitation requires authenticated query access.
TRIAGE SIGNALaffects cloud control plane / managed runtime that customer cannot patch
TRIAGE REASONINGManaged database service vulnerability requiring customer action; control plane component customers cannot patch themselves.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune +https://aws.amazon.com/security/security-bulletins/rss/2026-136-aws/ +Thu, 15 Oct 2026 16:41:28 +0000 + +Bulletin ID: 2026-136-AWS + +Scope: AWS + +Content Type: Important (requires attention) + +Publication Date: 10/15/2026 09:30 AM PDT +Description: +Amazon Neptune is a fully managed graph database service. We identified CVE-2026-110812, an issue in Apache TinkerPop related to Gremlin functionality used by Amazon Neptune. Under certain conditions, an authenticated principal with Neptune data-plane (query) permissions could submit a request that causes the query engine to process untrusted input unsafely, which could lead to unintended activity within the query engine environment. This issue has been addressed in the engine versions listed below; we recommend customers upgrade. +Impacted versions: >=1.2.0.0 +Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, not independent arithmetic verification. A wrong figure in them has been corrected (config/corrected-text.yaml); the model's wording is kept, struck through, under the original text, and in data.json under original.triage.
| triage verdict | MATERIAL at 0.92, needed 0.55 |
|---|---|
| triage reasoning | Managed database service vulnerability requiring customer action; customers upgrade to a patched engine version or receive it through auto minor version upgrade. |
| signals | AWS managed service (Neptune) affected · deserialization vulnerability in query engine · authenticated attacker can trigger unsafe processing · affects the Neptune query engine; fixed in engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0 · requires upgrade action · broad version range affected (>=1.2.0.0) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |