Quick answers
- Is CVE-2026-110812 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110812 being exploited in the wild.
- How severe is CVE-2026-110812?
- Critical severity, with a CVSS score of 9.9, published 15 October 2026.
- Which products and versions are affected?
- Amazon Neptune >=1.2.0.0.
- Is there a fix for CVE-2026-110812?
- Yes: fixed in Neptune engine versions 1.4.7.1, 1.4.8.1, and 1.5.0.0. Until then: Until you upgrade, restrict Neptune neptune-db (query) permissions only to trusted principals, following least-privilege access practices. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110812 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-110812?
- Check whether you run Amazon AWS or Amazon Neptune at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Neptune engine versions 1.4.7.1, 1.4.8.1, and 1.5.0.0
Until you upgrade, restrict Neptune neptune-db (query) permissions only to trusted principals, following least-privilege access practices.
Technical details
This is a deserialization of untrusted data vulnerability in Apache TinkerPop's Gremlin functionality as used by Neptune. An authenticated principal with Neptune data-plane (query) permissions can submit a specially crafted request that causes the query engine to process untrusted input unsafely, leading to unintended activity within the query engine environment. The vulnerability affects Neptune engine versions 1.2.0.0 and later, and a fix is available.
Affected products
- Amazon Neptune >=1.2.0.0
Timeline
- 2026-10-15: disclosed