Back to Signal Feed
CodeTracked since May 19, 2026

PraisonAI now requires explicit SurrealDB credentials

The patch removes the SurrealDB default root/root login path and makes SurrealDB knowledge-store initialization require explicit username/password credentials, replacing an insecure implicit default.

PraisonAISurrealDBknowledge storedefault credentials

What Happened

  • The patch removes the SurrealDB default root/root login path and makes SurrealDB knowledge-store initialization require explicit username/password credentials, replacing an insecure implicit default.
  • The patch removes the SurrealDB default root/root login path and makes SurrealDB knowledge-store initialization require explicit username/password credentials, replacing an insecure implicit default.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced an authentication hardening change by eliminating the baked-in default credentials for SurrealDB and enforcing explicit username/password input when creating the knowledge store.

Why Track This

Why It Matters

Developers and operators running PraisonAI with SurrealDB will no longer have hidden exposure from default privileged credentials, reducing the chance of unintended database access after deployment. This is implemented by removing the root/root default path and requiring explicit credentials in initialization; environments that still rely on default authentication will now fail to connect until updated, so deployment manifests, Docker/env setups, and local scripts should be checked to ensure credentials are correctly provisioned and secret rotation is enforced after rollout.

Impact

Developers and operators running PraisonAI with SurrealDB will no longer have hidden exposure from default privileged credentials, reducing the chance of unintended database access after deployment. This is implemented by removing the root/root default path and requiring explicit credentials in initialization; environments that still rely on default authentication will now fail to connect until updated, so deployment manifests, Docker/env setups, and local scripts should be checked to ensure credentials are correctly provisioned and secret rotation is enforced after rollout.

What To Watch Next

  • Watch whether PraisonAI becomes a repeated pattern.
  • Track follow-up changes around AI Security.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: default_credentials_removed, legacy_configs_break.
Open Topic TimelineOpen Technical EventOpen Original Sourcedefault_credentials_removed / legacy_configs_break / credential_migration_required

Supporting Evidence