{"id":"CVE-2026-110812","kind":"vulnerability","aliases":["CVE-2026-110812"],"related":[],"title":"Amazon Neptune: Gremlin import lets an authenticated query user run code","description":"CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune\n\n### CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune\n\nBulletin ID: 2026-136-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/15/2026 09:30 AM PDT\n\nDescription:\n\nAmazon 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.\n\nImpacted versions: >=1.2.0.0\n\nResolution:\n\nThis issue has been addressed in Amazon Neptune engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0. We recommend upgrading your Amazon Neptune DB cluster to the corresponding patched version for your engine line. Customers with auto minor version upgrade enabled will receive the update during their next maintenance window; customers who manage engine versions manually should upgrade.\n\nWorkarounds:\n\nThis issue requires an authenticated principal with data-plane access. Until you can upgrade, follow least-privilege practices and grant Neptune neptune-db (query) permissions only to trusted principals. Upgrading your DB cluster to a patched Neptune engine version is the recommended remediation.\n\nReferences:\n\n- CVE-2026-110812\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"Amazon Neptune's Gremlin graph-import path deserializes untrusted input unsafely, a flaw inherited from Apache TinkerPop. An authenticated principal with Neptune query permissions can cause unintended activity inside the query engine environment.","severity":"critical","cvss":9.9,"epss":0.00365,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["amazon-neptune","aws","graph-database","gremlin","infrastructure","lab-disclosure"],"not_affected_if":["no-untrusted-query-access","patched-engine-version"],"how_to_check":"- Check the Neptune DB cluster engine version in the AWS console or with `aws neptune describe-db-clusters --query 'DBClusters[].EngineVersion'`\n- Review which principals hold neptune-db query permissions (IAM policies using `neptune-db:*` or `neptune-db:ReadDataViaQuery` / `neptune-db:WriteDataViaQuery`)","fix":"- Upgrade the Neptune engine to `1.4.7.1`, `1.4.8.1` or `1.5.0.0` matching your engine line\n- Until upgraded, restrict neptune-db query permissions to trusted principals only","status":"open","published_at":"2026-10-15T00:00:00+00:00","first_seen_at":"2026-10-24T18:56:54+00:00","triaged_at":"2026-10-25T02:59:37+00:00","updated_at":"2026-10-25T12:38:49+00:00","category":"infrastructure","confidence":0.7,"triage":{"at":"2026-10-25T02:59:37Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade the Neptune engine to `1.4.7.1`, `1.4.8.1` or `1.5.0.0` matching your engine line\n- Until upgraded, restrict neptune-db query permissions to trusted principals only","reach":"network","title":"Amazon Neptune: Gremlin import lets an authenticated query user run code","impact":"high","summary":"Amazon Neptune's Gremlin graph-import path deserializes untrusted input unsafely, a flaw inherited from Apache TinkerPop. An authenticated principal with Neptune query permissions can cause unintended activity inside the query engine environment.","category":"infrastructure","nicknames":[],"who_cares":["aws","amazon-neptune","graph-database","gremlin"],"confidence":0.7,"needs_auth":"yes","worst_case":"Authenticated query user triggers unsafe deserialization inside the query engine","analyst_note":"Confirm the exact unintended-activity outcome and whether the AWS bulletin 2026-136-AWS lists any further exploitation details or affected engine lines below 1.2.0.0.","how_to_check":"- Check the Neptune DB cluster engine version in the AWS console or with `aws neptune describe-db-clusters --query 'DBClusters[].EngineVersion'`\n- Review which principals hold neptune-db query permissions (IAM policies using `neptune-db:*` or `neptune-db:ReadDataViaQuery` / `neptune-db:WriteDataViaQuery`)","needs_analyst":true,"not_affected_if":["patched-engine-version","no-untrusted-query-access"],"who_is_affected":"Teams running Amazon Neptune engine versions `>=1.2.0.0` that let identities submit Gremlin queries to the database. Exposure depends on who holds data-plane query permissions, since the flaw needs an authenticated principal. Clusters on patched engine lines or with no untrusted query access can deprioritize the patch only briefly.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"critical"},"cost_usd":0.000752,"input_tokens":3933,"output_tokens":718,"severity_before":"critical"},"analyst_status":null,"analyst_note":null,"search":"'-110812':14A,17A,66C,83C,131C,307C '-136':101C '-2026':13A,16A,65C,82C,130C,306C '09':113C '1.2.0.0':200C '1.4.7.1':212C '1.4.8.1':213C '1.5.0.0':215C '10/15/2026':112C '2026':100C '30':114C 'access':268C 'activ':58B,177C 'address':187C,206C 'amazon':1A,19B,30B,79C,96C,118C,143C,208C,220C 'amazon-neptun':18B 'apach':46B,135C 'attent':109C 'authent':7A,49B,149C,262C 'auto':235C 'aw':21B,102C,104C 'aws-security@amazon.com':310C 'bulletin':98C 'caus':56B,163C 'certain':146C 'cluster':223C,293C 'code':11A 'concern':316C 'condit':147C 'content':105C 'correspond':226C 'could':158C,173C 'custom':196C,233C,249C 'cve':12A,15A,64C,81C,129C,305C 'data':70C,87C,154C,266C 'data-plan':153C,265C 'databas':24B,125C 'date':111C 'db':222C,283C,292C 'descript':117C 'deseri':38B,67C,84C 'disclosur':29B 'email':309C 'enabl':239C 'engin':62B,166C,181C,190C,210C,231C,252C,298C 'environ':63B,182C 'flaw':43B 'follow':273C 'fulli':122C 'function':140C 'grant':279C 'graph':23B,35B,75C,92C,124C 'graph-databas':22B 'graph-import':34B,74C,91C 'gremlin':3A,25B,33B,73C,90C,139C 'id':99C 'identifi':128C 'impact':198C 'import':4A,36B,76C,93C,107C 'infrastructur':26B 'inherit':44B 'input':40B,170C 'insid':59B 'issu':133C,184C,203C,259C 'lab':28B 'lab-disclosur':27B 'lead':174C 'least':275C 'least-privileg':274C 'let':5A 'line':232C 'list':192C 'mainten':247C 'manag':123C,251C 'manual':254C 'minor':236C 'neptun':2A,20B,31B,52B,80C,97C,119C,144C,152C,209C,221C,280C,282C,297C 'neptune-db':281C 'next':246C 'patch':227C,296C 'path':37B,77C,94C 'pdt':116C 'permiss':54B,157C,285C 'plane':155C,267C 'pleas':308C 'practic':277C 'princip':50B,150C,263C,289C 'privileg':276C 'process':168C 'public':110C 'queri':8A,53B,61B,156C,165C,180C,284C 'question':314C 'receiv':241C 'recommend':195C,217C,302C 'refer':304C 'relat':137C 'remedi':303C 'request':161C 'requir':108C,260C 'resolut':201C 'run':10A 'scope':103C 'secur':313C 'servic':126C 'submit':159C 'tinkerpop':47B,136C 'trust':288C 'type':106C 'unintend':57B,176C 'unsaf':41B,171C 'untrust':39B,69C,86C,169C 'updat':243C 'upgrad':197C,218C,238C,256C,272C,290C 'use':141C 'user':9A 'version':191C,199C,211C,228C,237C,253C,299C 'window':248C 'within':178C 'workaround':257C","nicknames":[],"mitigations":[],"who_affected":"Teams running Amazon Neptune engine versions `>=1.2.0.0` that let identities submit Gremlin queries to the database. Exposure depends on who holds data-plane query permissions, since the flaw needs an authenticated principal. Clusters on patched engine lines or with no untrusted query access can deprioritize the patch only briefly.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-15T00:00:00+00:00","kev":null,"cvss_vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"ff89ba41-3aa1-4d27-914a-91399e9639e5","poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/rss/2026-136-aws/#CVE-2026-110812","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-136-aws/","severity":null,"published_at":"2026-10-15T00:00:00+00:00","modified_at":null,"first_seen_at":"2026-10-24T18:56:54+00:00","fetched_at":"2026-10-24T18:56:54+00:00","note":"AWS: CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune"},{"source":"nvd","external_id":"CVE-2026-110812","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-110812","severity":null,"published_at":"2026-10-15T17:17:16+00:00","modified_at":"2026-10-16T19:17:03+00:00","first_seen_at":"2026-10-24T19:23:38+00:00","fetched_at":"2026-10-24T19:23:38+00:00","note":null},{"source":"epss","external_id":"CVE-2026-110812","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-110812","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-25T12:38:49+00:00","fetched_at":"2026-10-25T12:38:49+00:00","note":null}],"documents":[{"id":2909,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-136-aws/","title":"AWS: CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune","kind":"advisory","source":"lab","text":"CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune\n\n### CVE-2026-110812 - Deserialization of untrusted data in the Gremlin graph-import path in Amazon Neptune\n\nBulletin ID: 2026-136-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/15/2026 09:30 AM PDT\n\nDescription:\n\nAmazon 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.\n\nImpacted versions: >=1.2.0.0\n\nResolution:\n\nThis issue has been addressed in Amazon Neptune engine versions 1.4.7.1, 1.4.8.1 and 1.5.0.0. We recommend upgrading your Amazon Neptune DB cluster to the corresponding patched version for your engine line. Customers with auto minor version upgrade enabled will receive the update during their next maintenance window; customers who manage engine versions manually should upgrade.\n\nWorkarounds:\n\nThis issue requires an authenticated principal with data-plane access. Until you can upgrade, follow least-privilege practices and grant Neptune neptune-db (query) permissions only to trusted principals. Upgrading your DB cluster to a patched Neptune engine version is the recommended remediation.\n\nReferences:\n\n- CVE-2026-110812\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":"2026-10-15T00:00:00+00:00","relation":"advisory","confidence":null,"note":null}],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}