Release Date: 8 July 2026

Release Note for Neo4j 2026.06.0 (8 July 2026)

 

Advanced notice of changes scheduled for after 2026.LTS

Read more  

Server

  • Preview feature: an improved vector search that uses our new Hi-Fidelity Quantized Vector Search method. HFQ performs an initial expanded search on the quantized vectors, then re-ranks the results using the full precision vectors. This should make queries faster, reduce memory requirements, and increase recall accuracy when compared to the previous default quantized vector index.

HFQ adds the following options to CREATE VECTOR INDEX, vector.quantization.type and vector.default_search_expansion_factor.

To try the preview of HFQ:

CREATE VECTOR INDEX moviePlots IF NOT EXISTS

FOR (m:Movie)

ON m.embedding

OPTIONS { indexConfig: {

`vector.quantization.type`: ‘binary’,

`vector.default_search_expansion_factor`: 2.0,

`vector.dimensions`: 1536,

`vector.similarity_function`: ‘cosine’,

}}

HFQ requires an index re-build and is expected to be GA in the next release.

 

Neo4j-admin

 

Attribute-Based Access Control

  • Attribute-Based Access Control (ABAC) is now supported for native and native linked LDAP users in addition to externally authenticated SSO users. New user metadata tagging feature enables administrators to assign tags to native DBMS users.  These user tags can be part of an ABAC rule to provide dynamic role assignment. See Operations Manual -> Attribute-based access control, Manage users, and DBMS USER METADATA MANAGEMENT privileges.
 

Security

 

Cypher

Cypher 25 Features

  • CALL { … } IN CONCURRENT TRANSACTIONS now supports DISJOINT BY  a deadlock prevention mechanism that eliminates lock contention in parallel write workloads natively. High concurrency ingestion, particularly when merging nodes with unique constraints or creating relationships, has always been vulnerable to deadlock, as parallel threads compete for the same locks simultaneously. DISJOINT BY resolves contention at scheduling time, before any transaction is attempted. See the Cypher Manual -> Batch scheduling and deadlock prevention with DISJOINT BY.
  • GRAPH TYPE moves from public preview to GA in this release. You can now define, enforce, and validate your graph schema at the database level in production workloads with the stability guarantees that come with a fully supported feature. See the Cypher Manual -> Graph types.
  • Extend SHOW CURRENT GRAPH TYPE to be able to return lists of virtual nodes and relationships representing the graph type (similar in format to the output of db.schema.visualization()) instead of the current string representation. To get the graph version of the command, use SHOW CURRENT GRAPH TYPE AS GRAPH. See the Cypher Manual -> SHOW CURRENT GRAPH TYPE AS GRAPH.
  • For customers using Change Data Capture (CDC), we have added a txCommitTime column to db.cdc.current() procedure. This update allows clients to conveniently identify the commit time of their most recent transaction alongside the transaction identifier. See the Operations manual -> Built-in procedures.
  • Vector SEARCH queries now support IN for filtering, allowing queries like:

MATCH (movie:Movie)

        SEARCH movie IN (

          VECTOR INDEX moviePlots

          FOR $queryVector

          WHERE movie.genre IN [“Horror”, “SciFi”]

          LIMIT $topK

        )

RETURN movie.title AS title, movie.rating AS rating

See the Cypher Manual -> Predicates for vector search with filters.

 

Bug fixes

Server

  • Fixed a bug that allowed cached pages to exceed the configured limit.
  • Fixed a bug where outbound network chunks for secondaries were not flushed properly. This could lead to a buffer overflow in the outbound.

Cypher

  • Fixed a bug in the pipelined runtime where an OR EXISTS subquery containing ordering could silently drop a result row:

MATCH (c:Customer) WHERE c.vipStatus = true OR EXISTS { MATCH (c)-[:PLACED]->(o:Order) RETURN o ORDER BY o.total DESC } RETURN c.name

  • Fixed a record format bug where undirected scans of multiple relationship types omitted sibling relationships, resulting in a ~50% undercount in the output.
  • Fixed an issue that let a User Defined Function (UDF) be defined as part of a Property-Based Access Control (PBAC) privilege. This isn’t supported and wouldn’t have worked as a user might have expected.  
  Please refer to the changelog for full details of the changes.  

Bundled products

The following products have been included in the distribution – available in /products directory unless stated otherwise – and are fully compatible with this release.
  • APOC Core 2026.06.0 – The most popular community library developed for the database, is fully supported (included in Labs directory).
  • Bloom 6.x-2.34.0 – A beautiful and expressive data visualization tool to quickly explore and interact with Neo4j’s graph data platform – no coding required. Please refer to the release notes for details.  (Requires a License)
  • Browser 2026.07.02+0  – Neo4j Browser is a tool for developers to interact with the graph. It is the default interface for both Enterprise and Community Editions (included in the /libs directory) of the Neo4j database.
  • Neo4j GenAI Plugin 2026.06.0 – Neo4j’s GenAI plugin provides functions and procedures to interact with external AI providers through Cypher, such as for creating vector embeddings and generating text.
  • Neo4j Graph Data Science 2026.06.0 is a compatible version of the connected data analytics and machine learning platform that helps you understand the connections in big data to answer critical questions and improve predictions. Please refer to the release notes for further details. (GDS Enterprise requires a License. )
  • Enterprise Fleet Management is no longer bundled with the DBMS package as it is now included in Neo4j.
  • Neo4j Ops Manager 1.15.2 is a UI-based tool that enables Administrators to operate and observe all of their Neo4j Database Management Servers. Now includes support for Neo4j’s any-to-any upgrade. Please refer to the release notes for details. (Included in Enterprise).
   

Advanced notice of upcoming changes

Query Log Default Format

The default query log format for new installations will change after the next Long Term Support (LTS) release. At the moment, it is set to PLAIN format by default. From the release after the next LTS, the default will be JSON format. If you are upgrading and preserving your current server-logs.xml file, then there will be no change, as support for PLAIN will remain, only the default value for new installations is changing. We recommend moving to JSON for query logging as it contains more information, though the resulting log file size will increase.  

High_limit store format

Heads-up: High_limit store format removal after the next LTS The High_limit store format was deprecated in Neo4j 5.23. The upcoming long-term support (LTS) release will be the final version to support reading, writing, and migrating High_limit databases. Beyond that LTS, Neo4j will not start if it detects a High_limit store. Please take note of the following:
  • The next LTS is the last supported migration window. Reading, writing, and migrating High_limit databases remains supported until the next LTS release only.
  • Databases using the High_limit format will fail to start after the next LTS. No fallback or compatibility layer will be available.
  • Migration to the Block format is required before upgrading beyond the next LTS. We strongly recommend planning and completing your offline migration during or prior to your upgrade to that LTS release.
 

Recent Database Releases

See All Database Releases →