sudo docker logs -f Vaultwarden | grep Version
| Version 1.36.0 |
Logs
No response
Screenshots or Videos
No response
Additional Context
Just caused some moments of concern after the CVE notification when I thought my container was out of date. I double checked the startup logs and saw the discrepency.
Outside that, thanks for all your work on this project.
Originally created by @articuno1au on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7184
### 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
Not applicable.
### Vaultwarden Build Version
1.36.0
### Deployment method
Official Container Image
### Custom deployment method
_No response_
### Reverse Proxy
Traefik
### Host/Server Operating System
Linux
### Operating System Version
_No response_
### Clients
CLI
### Client Version
_No response_
### Steps To Reproduce
Run `docker inspect Vaultwarden | grep version` and note the `org.opencontainers.image.version` label.
Run `docker logs Vaultwarden | grep Version` and note the included version from startup.
The two versions do not match, with the container listing 1.35.8, and the application 1.36.0
### Expected Result
Both the container image version and the application version should match.
### Actual Result
```
sudo docker inspect Vaultwarden | grep -i version
"com.docker.compose.version": "5.1.3",
"org.opencontainers.image.version": "1.35.8",
```
```
sudo docker logs -f Vaultwarden | grep Version
| Version 1.36.0 |
```
### Logs
_No response_
### Screenshots or Videos
_No response_
### Additional Context
Just caused some moments of concern after the CVE notification when I thought my container was out of date. I double checked the startup logs and saw the discrepency.
Outside that, thanks for all your work on this project.
GiteaMirror
added the bug label 2026-06-17 09:52:20 -05:00
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 @articuno1au on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7184
Prerequisites
Vaultwarden Support String
Not applicable.
Vaultwarden Build Version
1.36.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Traefik
Host/Server Operating System
Linux
Operating System Version
No response
Clients
CLI
Client Version
No response
Steps To Reproduce
Run
docker inspect Vaultwarden | grep versionand note theorg.opencontainers.image.versionlabel.Run
docker logs Vaultwarden | grep Versionand note the included version from startup.The two versions do not match, with the container listing 1.35.8, and the application 1.36.0
Expected Result
Both the container image version and the application version should match.
Actual Result
Logs
No response
Screenshots or Videos
No response
Additional Context
Just caused some moments of concern after the CVE notification when I thought my container was out of date. I double checked the startup logs and saw the discrepency.
Outside that, thanks for all your work on this project.