Skip to content

Incident detail

Public role privilege modification impacted for some Business Critical instances

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Neo4j Aura breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Identified

    We have identified an issue where the PUBLIC role cannot be modified on certain Business Critical instances.

    The public role is available to all database users, and contains a limited set of privileges outlined in our documentation: https://neo4j.com/docs/operations-manual/current/authentication-authorization/built-in-roles/#access-control-built-in-roles-public

  2. Identified

    We have identified the issue and a fix is being rolled out

  3. Resolved

    We have applied a fix and verified this is fully resolved.

  4. Resolved

    ## What happened

    On June 27th, the new predefined roles feature*  for AuraDB customers inadvertently removed database Admin access from some Business Critical (BC) instances. As a temporary fix, the team disabled the feature for Business Critical instances. While the fix took place, it also replaced the database public RBAC role privileges which are available on Business Critical with enhanced public role privileges available on Free/Pro instances. System logic prevented customers from modifying the public role during that time.*https://neo4j.com/docs/aura/user-management/#_predefined_roles

    Neo4j restored the public role to its original limited permissions for all Virtual Dedicated Cloud instances on June 30, and for all Business Critical instances on July 1.

    ## How customers were affected

    Customers were affected by this issue from June 27th to July 1st.  The issue impacted some Business-Critical (BC) instances and a small number of Virtual Dedicated Cloud (VDC) instances. All project admin users with affected instances received an email confirming the issue was resolved on July 1st.

    ## What we are doing now

    Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future:

    • We have implemented safeguards in our system to prevent misconfigured role changes and better isolate feature toggles from production permission models
    • We are reviewing our internal release processes to improve testing and validation of role-based access control (RBAC) changes
    • We are implementing additional detection methods for misconfigured RBAC which will alert our operational teams

Keep exploring

More from Neo4j Aura

Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.