Release Date: 26 January 2026

The Neo4j Aura January SECOND release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.

Release Note for Neo4j 2026.01 (Release date: 26 January 2026)

Server

Public preview: Vector search with filters supported by in-index filtering and new Cypher syntax for querying vectors. See blog post.

Fixed a bug when deleting a relationship property that was added or changed in the same transaction, which in some cases could cause a NullPointerException and failing the transaction.

Fixed stack overflows when traversing long lists constructed by append/prepend.
Fixed a bug where SHORTEST 1 would return a path shorter than the lower bound of the variable-length pattern.

Update:

During the rollout of Neo4jAura 2026.01, a bug was identified in conditional queries where WHEN clauses did not correctly handle null values when no grouping key was present. The issue was fixed and the release then proceeded to higher tiers. More details on Status Page.

During the roll of Neo4j 2025.11, a bug in Dynamic Node Labels and Dynamic Relationship Types was identified. It happened when used with composite (multi-property) indexes, which could lead to the operator sometimes returning incorrect MATCH results. This could also potentially result in updates to the incorrect node, or in the runtime issuing CREATE operations that cannot succeed. The fix has been released and rolling out to higher tiers, but in the meantime we advise customers not to use Dynamic Label/Relationship Types in conjunction with composite indexes.

Please refer to the changelog for full details of the changes, and Neo4j Release notes for all changes to other Neo4j products and services.

The Neo4j Aura January release has started to roll out, commencing on AuraDB Free and progressing to higher tiers later.

Fixed an issue where we could underestimate the heap usage of DISTINCT in Cypher queries. For queries with very large DISTINCT sets this could lead to a JVM OutOfMemoryError instead of the normal recoverable “The memory pool limit was exceeded” error.
Fixed a bug where using a subquery expression in allReduce() initializer would fail with an error like Did not find UNNAMED9 in the slot configuration.
Fixed a bug in parallel runtime queue maintenance where failed queries were holding on to heap memory for longer than necessary.
Fixed a bug when returning entities located inside a map or list where these were incorrectly evaluated due to a missing eager operator.

Please refer to the changelog for full details of the changes, and Neo4j Release notes for all changes to other Neo4j products and services.

See All Aura Releases →