Chrome extension fails CORS due to missing origin #1088

New Issue

MrUnknownDE · 2026-04-06T01:34:21+02:00

MrUnknownDE commented

2026-04-06 01:34:21 +02:00

Originally created by @RaidAndFade on 6/22/2024

Subject of the issue

Latest version of chrome bitwarden extension requires cors header response, which current codebase does not do.

Steps to reproduce

Download bitwarden chrome extension, try to use vaultwarden as a backend, all POST requests fail due to missing ORIGIN header

Expected behaviour

expect bitwarden extension works

Actual behaviour

bitwarden extension receives data but cannot push any new information to vault

Troubleshooting data

origin header is of format
Origin: chrome-extension://nngceckbfpebfimklniiiawkandclblb
Code found at https://github.com/dani-garcia/vaultwarden/blame/main/src/util.rs#L133 to allow the domain as well as safari extension "file://" but not chrome-extension prefix. Believe some work is doable there.

*Originally created by @RaidAndFade on 6/22/2024*   ### Subject of the issue  Latest version of chrome bitwarden extension requires cors header response, which current codebase does not do. ### Steps to reproduce  Download bitwarden chrome extension, try to use vaultwarden as a backend, all POST requests fail due to missing ORIGIN header ### Expected behaviour  expect bitwarden extension works ### Actual behaviour  bitwarden extension receives data but cannot push any new information to vault ### Troubleshooting data  origin header is of format Origin: chrome-extension://nngceckbfpebfimklniiiawkandclblb Code found at https://github.com/dani-garcia/vaultwarden/blame/main/src/util.rs#L133 to allow the domain as well as safari extension "file://" but not chrome-extension prefix. Believe some work is doable there.

MrUnknownDE closed this issue

2026-04-06 01:34:21 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1088