panic error on start

[jirireischig]

Prerequisites

• I have searched the existing Closed AND Open Issues AND Discussions
• I have searched and read the documentation

Vaultwarden Support String

I can't find it.

Vaultwarden Build Version

1.35.7

Deployment method

OS Package (apt, yum/dnf, pacman, apk, nix, ...)

Custom deployment method

No response

Reverse Proxy

apache

Host/Server Operating System

Linux

Operating System Version

Rocky Linux 8.10

Clients

Web Vault

Client Version

No response

Steps To Reproduce

After update to version 1.35.7 I got error after start:

[2026-05-19 14:28:32.211][panic][ERROR] thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Serde.
[CAUSE] Error("EOF while parsing a value", line: 1, column: 0)': src/main.rs:89
   0: vaultwarden::init_logging::{{closure}}
   1: std::panicking::panic_with_hook
   2: std::panicking::panic_handler::{closure#0}
   3: std::sys::backtrace::__rust_end_short_backtrace::<std::panicking::panic_handler::{closure#0}, !>
   4: __rustc::rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: vaultwarden::main::{{closure}}
   8: vaultwarden::main
   9: std::sys::backtrace::__rust_begin_short_backtrace
  10: main
  11: __libc_start_main
  12: _start

Expected Result

Start without error

Actual Result

error

Logs

Screenshots or Videos

No response

Additional Context

No response

[BlackDex]

There seems to be an invalid 2FA record in your database for some reason.
I do find it strange it happend after your update, since that function was there before already, and has not been changed since i think, I'm not sure from which version you came, but 1.35.7 is also not the current latest stable version, that would be 1.36.0.

But, in any case, check your database, in the twofactor table for any record which has atype set to 4 and has either an empty data column, or not starting with either {" or [{", i think those should be the only starting items available in there.

[jirireischig]

All my records with atype set to 4 starting with [{".

[jirireischig]

The issue is caused by the MariaDB-shared package (/lib64/libmariadb.so.3) in the latest version, 10.11.17.
When I downgrade MariaDB-shared to 10.11.16 version Vaultwarden works OK.

[BlackDex]

Well, nice that MariaDB once again breaks stuff with a new version.

[jirireischig]

I tried upgrade MariaDB-shared package to latest version 10.11.18.
Start failed with this error:

May 29 13:51:23 vona.ecn.cz vaultwarden[10124]: [2026-05-29 13:51:23.539][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2026-04-25-120000_sso_auth_binding", version: MigrationVersion("20260425120000") }, DatabaseError(Unknown, "Duplicate column name 'binding_hash'"))': src/db/mod.rs:501
                                                   0: vaultwarden::init_logging::{{closure}}
                                                   1: std::panicking::panic_with_hook
                                                   2: std::panicking::panic_handler::{closure#0}
                                                   3: std::sys::backtrace::__rust_end_short_backtrace::<std::panicking::panic_handler::{closure#0}, !>
                                                   4: __rustc::rust_begin_unwind
                                                   5: core::panicking::panic_fmt
                                                   6: core::result::unwrap_failed
                                                   7: vaultwarden::db::DbPool::from_config
                                                   8: vaultwarden::main::{{closure}}
                                                   9: vaultwarden::main
                                                  10: std::sys::backtrace::__rust_begin_short_backtrace
                                                  11: main
                                                  12: __libc_start_main
                                                  13: _start

May be it helps to find solution for this problem.

[CountMurphy]

Ran into a similar issue with mariadb 12.3.2 here (bug 7268)

[teister]

[BlackDex]

Not sure what you expect from us? This is not a problem we can resolve.
It's an issue in MariaDB and it's library. And if you are not using the official Container Images, then you need to report this to the packager of the installation you use.