Import: import jmap no longer reads the shared ~/.config/inbuxa profile; it needs --url and the source server's own credentials. import-directory sends a profile's key only to that profile's own server. (advisory, medium)
Deps: rustls-webpki 0.103.17 and webpki-root-certs 1.0.12 (RUSTSEC-2026-0382/0383, distrusted emSign intermediates).
Tests: cargo test --locked (1733 passed) and cargo fmt --check pass locally; cargo-audit clean of both advisories.
Security fixes for 27.1-rc.16.
- Import: `import jmap` no longer reads the shared `~/.config/inbuxa` profile; it needs `--url` and the source server's own credentials. `import-directory` sends a profile's key only to that profile's own server. (advisory, medium)
- Deps: rustls-webpki 0.103.17 and webpki-root-certs 1.0.12 (RUSTSEC-2026-0382/0383, distrusted emSign intermediates).
Tests: `cargo test --locked` (1733 passed) and `cargo fmt --check` pass locally; cargo-audit clean of both advisories.
import jmap read the shared ~/.config/inbuxa profile, which names the
inbuxa server and holds its API key, and fell back to that key whenever no
flag or INBUXA_MIGRATE_* variable gave one -- even with a bare
--auth-bearer, which is documented to prompt. But import jmap reads FROM a
source server, often another provider's, so the inbuxa key went as a
bearer token to whatever --url named. An operator with a default profile
who ran import jmap against another server handed that server (or anyone
who controlled or watched the URL) an inbuxa administrator key.
import jmap no longer reads the profile: --url is required again,
--profile is gone from it, and the source's credentials come from a flag,
an INBUXA_MIGRATE_* variable or the prompt. import-directory, which does
write to the inbuxa server, keeps the profile, but now sends its key only
to the profile's own origin; a --url with another scheme, host or port gets
no key from the profile. The --url help, the README, usage.md and the
missing-secret message no longer describe import as writing to inbuxa.
Test: import_jmap_never_takes_the_url_or_key_from_the_profile and
import_directory_sends_the_profile_key_only_to_the_profile_url failed
before (the profile's url and key were used for import jmap, and the key
went to another --url on import-directory); both pass now.
The lockfile pinned rustls-webpki 0.103.15 and webpki-root-certs 1.0.9,
which still accept certificates chained through emSign intermediates that
are now distrusted (RUSTSEC-2026-0382, RUSTSEC-2026-0383). inbuxa-migrate
signs in to source mail servers over TLS with administrator credentials
(IMAP, JMAP, DAV, HTTP), so someone on the path holding such a certificate
could pose as the source and capture them.
rustls-webpki is now 0.103.17 and webpki-root-certs 1.0.12; nothing else
in the lockfile moves.
Test: cargo audit reported both advisories before; it reports neither now,
and cargo test --locked passes.
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.
Security fixes for 27.1-rc.16.
import jmapno longer reads the shared~/.config/inbuxaprofile; it needs--urland the source server's own credentials.import-directorysends a profile's key only to that profile's own server. (advisory, medium)Tests:
cargo test --locked(1733 passed) andcargo fmt --checkpass locally; cargo-audit clean of both advisories.