Changelog

Follow up on the latest improvements andĀ updates.

RSS

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Tidy Up Your Org with Automated User Pruning 🧹

Keep your security tight and your member list tidy without the manual effort. Our new
Inactive Organization Member Pruning
feature lets you automate the clean-up for users who no longer require access to your Aura Organization.
The Highlights:
  • Set Your Rules: Define a period (
    30
    –
    365
    days) after which inactive members are automatically removed from the Org.
  • Fair Warnings: Aura optionally sends up to
    three email notifications
    to users before they lose access, giving them plenty of time to log back in.
  • Activity Defined: Any action in the Console or via the Aura API resets the inactivity timer.
  • Built-in Safety: We’ll never remove the last Owner or Project Admin, and you can mark specific VIPs as Exempt.
  • Easy Recovery: Users automatically pruned can be re-invited to the org if they need to regain access.
Ready to declutter? Head to the Organization Security page to configure your policy. For further reading, our documentation page on inactive organization member pruning gives additional details.
(Note: This feature is unavailable for organizations using SSO as their exclusive login method. We recommend using the SSO provider's user management tools in these cases)

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Fleet Manager

Aura Console User Password Requirements

Boosting Your Aura Security šŸ”
To keep your graphs under lock and key, we’re rolling out a small update to our password policy and a friendly reminder about your security toolkit.
What’s Changing?
Starting today, the minimum password length for the Aura Console is increasing to
16
characters. This will apply to any new users, or any users that reset their password.
Why the change?
While "
Gr4ph123
" was a solid start, modern security standards have evolved. Experts such as NIST now agree that password length, combined with always using a unique password, are the best defense against attacks. A longer password creates exponentially more entropy, making it much harder for bad actors to guess, while remaining easier for humans to remember if you use a simple passphrase (e.g., Correct-Horse-Battery-Staple).
Level Up with MFA šŸ“±
A strong password is a great first layer, but why stop there? We highly recommend enabling Authenticator-based TOTP MFA (Time-based One-Time Password) as this is ultimately the best way to protect your Aura account.
How to do it:
  1. Log in to the Aura Console using email/password.
  2. Go to Account > Settings > Preferences > Security.
  3. Enable Multi-Factor Authentication (MFA).
  4. Follow the MFA set up steps.
If you are an Org admin, you can make Authenticator-based MFA mandatory for all of your org users in the Organization Security Settings. It only takes a minute, but it gives you peace of mind that lasts much longer.
Action Items for You
  • Update your password: If you're using a short password it is time to update it. The next time you change your password, you’ll be prompted to meet the new 16-character requirement.
  • Enable MFA: If you haven’t already, grab your favorite authenticator app (like Google Authenticator or Authy) and link it to your account.
Pro Tip: Using a password manager makes meeting this 16-character requirement a breeze. Let the robots do the remembering so you can focus on the querying!

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database April Release

The Neo4j Aura April release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
This release focuses on strengthening GQL compliance, expanding GenAI capabilities with new AI token functions, and improving memory efficiency for complex queries.
šŸš€ New Cypher 25 Features (GQL Standards)
We are continuing our commitment to GQL (Graph Query Language) standards by introducing new predicates and statements that align Cypher with international standards:
  • IS LABELED / IS NOT LABELED
    : New GQL-compliant predicates to test for node labels (equivalent to the existing
    IS
    and
    IS NOT
    syntax). More details on Cypher Manual.
  • FOR Statement
    : You can now use the GQL
    FOR
    statement to extract individual rows from a list (the GQL equivalent of
    UNWIND
    ).
šŸ¤– New AI Token Handling Functions
To further support GenAI and LLM integration workflows, we’ve added two new functions to help manage context windows and token limits:
  • ai.text.chunkByTokenLimit
    : Automatically split input strings into lists while respecting specific token limits. Link to Docs.
  • ai.text.countToken
    : Easily estimate the token count of a given string directly within your query. Link to Docs.
šŸ“ˆ Performance & Infrastructure Improvements
  • Memory Optimization
    : Significant reduction in memory usage for the
    SHORTEST
    statement and improved precision for memory tracking within the Top operator.
  • Parallel runtime
    memory tracking enhancements: Improved the precision of memory tracking within the Top operation.
  • Detailed
    version reporting
    in query output: EXPLAIN and PROFILE output now consistently includes the underlying Neo4j version, reporting down to the point release.
  • Drivers
    : Updated
    neo4j-java-driver
    and
    netty-bom
    .
šŸ› ļø Bug Fixes
  • Vector Indexing
    : Fixed an issue where quantized data in
    vector-3.0
    indexes wasn’t being utilized at query time. This fix reduces memory usage for vector searches without requiring an index rebuild.
  • RBAC/PBAC
    : Resolved an error that occurred when running duplicate Property-Based Access Control commands containing temporal functions.
  • Show Databases
    : Fixed an incorrect error message when passing a parameter with the incorrect type to SHOW DATABASES.
  • Stability
    : Fixed a rare record format bug related to iterating relationships on nodes that concurrently become dense.
  • Pathfinding
    : Fixed a bug where
    SHORTEST
    would occasionally omit valid paths when multiple targets were present.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – April 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database March SECOND Release

The Neo4j Aura March SECOND release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
This second release in March reveals excited new security features and Cypher 25 updates!
šŸ§‘šŸ»ā€šŸ’»Cypher 25: New Path Modes & Visibility
We’ve added several features to make your queries safer and more transparent:
  • ACYCLIC Path Mode
    : You can now specify that a node cannot be traversed more than once in a pattern match, avoiding loops.
  • LOAD CSV Progress Tracking
    : Use
    SHOW TRANSACTIONS
    to see real-time progress metrics for ingestion jobs.
  • GQL Conformance
    : We’ve added the
    PROPERTY_EXISTS()
    function to keep your code aligned with the latest GQL standards.
šŸš› Fleet Manager Updates
These apply if you are running Self-managed Neo4j instances, and upgraded the Neo4j version of your instances to 2026.03:
  • Built-in Fleet Manager
    : You won't need a plug-in to use Fleet Manager to manage your Self-managed Neo4j instances on Aura console anymore. It is ready by default.
  • Query Log Aggregation
    : You can now view aggregate query logs directly in the Aura console. Ensure
    db.logs.query.obfuscate_literals=true
    is set to enable this.
šŸ› ļø Bug and Security Fixes
  • Updated Jetty to v12.0.33 to resolve CVE-2026-1605.
  • Fixed a rare bug in the pipelined runtime involving EXISTS subqueries that could cause incorrect intermediate results.
  • Dynamic lookups now use locking index seeks when required, whereas previously they were vulnerable to constraint violations if used concurrently in a merge context.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – March 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database March Release

The Neo4j Aura March release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
šŸš€ Updates
  • New organizations created after 4 March default to Cypher 25. If you're an Organization admin, you can toggle the setting as needed.
  • Vector search with filters (in-index filtering) and the new Cypher
    SEARCH
    syntax for vector queries are now GA and supported for production use.
  • GRAPH TYPE
    is now available in Preview - It provides you the ability to declare your data model in a single, unified blueprint. This enforces strict data integrity including validation of relationship connections and label definitions without sacrificing the flexibility of an open schema.
  • Added GQL-compliant aliases for existing Cypher functions.
  • Added
    ai.text.structuredOutput()
    function to the GenAI Plugin, taking a textual prompt and map schema and outputting the result as a map adhering to the given schema.
šŸž Bug fixes
  • Fixed a bug in pipelined runtime where sometimes queries with multiple
    SelectOrSemiApply
    operators in the query plan could fail.
  • Fixed a bug where use of a composite property index in combination with a dynamic node label or dynamic relationship type could result in an incorrect
    MATCH
    result being returned.
  • Fixed issue with conditional query
    WHEN
    not aggregating null values correctly without a grouping key.
  • Fixed a bug with the new MergeUniqueNode operator.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – March 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database January SECOND Release - Update!

The Neo4j Aura January SECOND release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
This second release in January reveals excited new features of Vector Search!
šŸ›”ļø Vector Search
  • Vector Search with Filters
    : With this preview feature, you can now apply filters to your sector searches to narrow down your results.
  • Multiple Label Support
    : Vector Search in Cypher now supports multiple labels, giving you more flexibility in categorizing and querying your embedded data.
šŸž Bug fixes
Server
  • Fixed a
    NullPointerException
    that occurred when deleting a relationship property that had been modified within the same transaction.
Cypher
  • Fixed a stack overflow issue that occurred when traversing very long lists built using append or prepend operations
  • Resolved a bug where
    SHORTEST 1
    could incorrectly return a path shorter than the defined lower bound of a variable-length pattern.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – January 2026.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Console moving to console.neo4j.io

We previously communicated that the Aura Console would be moving to the console.neo4j.io domain. This change has now been completed.
No action is required for this update. However, as noted in earlier direct communications, customers who use
neo4j-admin
to upload backup files to Aura must upgrade to the 2025.04 release.
This upgrade ensures continued compatibility for neo4j-admin database upload commands (specifically neo4j-admin push to cloud on version 4) with the unified Neo4j Aura Console.
Users of
Explore
in the Aura Console may notice that some Perspectives stored in browser local storage are not visible on the new domain. These Perspectives are still accessible via console-preview.neo4j.io. A Knowledge Base article is linked from Explore and explains how to migrate these Perspectives to the new domain if needed.
This change does not impact any instances participating in the Bloom Enterprise EAP for Scene saving and Perspective sharing.
Users of
Query
and
Dashboards
may notice history and styling are not persisted after the move. You can read more about how to recover them by reading a separate Knowledge Base article.
If you experience any issues, please reach out to Neo4j Customer Support.
Thanks,
The Aura Team

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database January Release Update!

The Neo4j Aura January release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
This release focused on security patches and improvements in Cypher.
šŸ›”ļø Security fixes
We have patched the following libraries to resolve vulnerabilities:
  • LZ4
    : Updated to
    v1.10.1
    (Resolves CVE-2025-66566).
  • Jersey
    : Updated to
    v2.46
    (Resolves CVE-2025-12383).
šŸž Cypher Bug fixes
  • Improved Memory Tracking
    : Fixed an issue where
    DISTINCT
    operations could underestimate heap usage. This ensures that queries exceeding memory pool limits return a recoverable error rather than triggering a JVM
    OutOfMemoryError
    .
  • Parallel Runtime Optimization
    : Resolved a bug where failed queries in the parallel runtime held onto heap memory longer than necessary.
  • Subquery Fix
    : Fixed a "slot configuration" error when using subquery expressions in
    allReduce()
    initializers.
  • Entity Mapping
    : Fixed a bug where entities returned inside a map or list were incorrectly evaluated due to a missing eager operator.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – January 2026.
Neo4j Aura DS Enterprise now supports IP Filtering, enabling you to define which IP address ranges can access your Graph Data Science deployment. This feature compliments the existing AuraDB IP Filtering and provides strong, lightweight network access control without requiring private endpoint setup. Users with Organization Admin privileges can manage filters via the Aura Console UI or Admin API, with support for up to 100 IP ranges.
Network security filters can be applied across a project or individual to each Aura instance for consistent access policies.
IP Filtering is ideal for securing public or hybrid deployments, limiting access to trusted networks, enforcing compliance boundaries, and streamlining development environments.
Available now for Aura DS Enterprise in addition to Aura Graph Analytics when used with AuraDB Business Critical & Virtual Dedicated Cloud tiers. See our IP Filtering documentation for more details.

new

AuraDB Virtual Dedicated Cloud

AuraDB Professional

AuraDB Free

AuraDS Professional

AuraDS Enterprise

AuraDB Business Critical

Neo4j Aura Database December Release Update!

The Neo4j Aura December release is now rolling out—starting with AuraDB Free and gradually extending to higher-tier instances.
šŸ¤– GenAI Plug-in
We have expanded our GenAI capabilities with native functions and procedures for major providers (e.g. OpenAI, Azure OpenAI, Google VertexAI, and Amazon Bedrock):
  • Vector Embeddings
    : Use the new
    ai.text.embed
    function and
    ai.text.embedBatch
    procedure to generate Neo4j vector types directly from your data.
  • Text Completion
    : Generate text from prompts using the new
    ai.text.completion
    function.
  • Provider Management
    : Easily list allowed providers and configuration requirements with
    ai.text.embed.providers
    and
    ai.text.completion.providers
    .
šŸš€ New Cypher Features and Performance Improvements
  • Collection Functions
    : We have expanded the Cypher 25 capabilities with a suite of new collection-based functions, including
    coll.distinct
    ,
    coll.flatten
    ,
    coll.sort
    ,
    coll.insert
    , and more to give you finer control over your data structures.
  • Faster Dynamic Labels
    :
    MATCH
    and
    MERGE
    queries utilizing dynamic labels (e.g.,
    MATCH (p:$("Person"))
    ) now leverage property indexes, resulting in significantly faster performance.
  • Optimized Merge Operations
    : We’ve introduced two new planner operators:
    MergeUniqueNode
    to speed up merge queries with uniqueness constraints, and
    MergeInto
    to improve performance on pattern creation queries.
šŸž Security and Bug Fixes
  • Security
    : Resolved CVE-2025-12738 to tighten permission on property setting on and CVE-2025-11602 on Bolt protocol.
  • Fixed bugs related creation of full-text indexes, corrected error code 42N68 to 42I58 and fixed
    ArrayIndexOutOfBoundsException
    when using Label, Type, or property names longer than 2000 characters.
For full details of all updates and fixes in this release, please visit: Release Notes: Neo4j Aura Database – December 2025.
.
Load More
→