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
Originally created by @jirireischig on GitHub (May 19, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7240
### Prerequisites
- [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=)
- [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/)
### 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
```text
```
### Screenshots or Videos
_No response_
### Additional Context
_No response_
GiteaMirror
added the bug label 2026-07-17 20:28:06 -05:00
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.
<!-- gh-comment-id:4488496588 -->
@BlackDex commented on GitHub (May 19, 2026):
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.
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.
<!-- gh-comment-id:4488497347 -->
@jirireischig commented on GitHub (May 19, 2026):
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jirireischig on GitHub (May 19, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7240
Prerequisites
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:
Expected Result
Start without error
Actual Result
error
Logs
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub (May 19, 2026):
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
twofactortable for any record which hasatypeset to4and has either an emptydatacolumn, or not starting with either{"or[{", i think those should be the only starting items available in there.@jirireischig commented on GitHub (May 19, 2026):
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 commented on GitHub (May 19, 2026):
Well, nice that MariaDB once again breaks stuff with a new version.