-
v27.1-rc.16
Pre-Releasereleased this
2026-11-18 01:33:27 +00:00 | 2 commits to main since this releaseThe sixteenth release candidate of the 27.1 series: a security fix for
import jmap, which could send the inbuxa profile's API key to the source
server, and certificate checks that no longer trust the distrusted emSign
intermediates.Security
import jmapno longer sends the inbuxa server's API key to the source.
With no source token given, or--auth-bearergiven with no value, it
took the API key from the default~/.config/inbuxaprofile and sent it
to the source server as a bearer token, so whoever runs or watches that
server could take over the inbuxa server the profile names. Affected
27.1-rc.13 to 27.1-rc.15; migrations the server runs itself were not
affected. If you ranimport jmapwith a profile holding an API key and
no source token, rotate that key. (GHSA-x8xv-p366-95w2)- TLS certificate checks no longer accept certificates chained through the
distrusted emSign intermediates (rustls-webpki 0.103.17, webpki-root-certs
1.0.12; RUSTSEC-2026-0382, RUSTSEC-2026-0383).
Found by Coffey Labs.
Changed
import jmapno longer reads the shared profile, so what 27.1-rc.13 added
for it no longer applies: it needs--urlagain and the source's own
credentials (a flag, anINBUXA_MIGRATE_*variable or the prompt), and
--profileis gone from it.import-directorystill reads the profile, but sends its API key only to
that profile's own server (the same scheme, host and port). With a
--urlfor another server, the key comes from a flag, a variable or the
prompt.
Binaries for linux/amd64 and linux/arm64. Verify with SHA256SUMS (signed as SHA256SUMS.minisig; minisign public key in the README).
Downloads