Repository navigation
Description
Bug Description
livekit-plugins-noise-cancellation (latest 0.3.2, released 2026-09-15) still trusts the compromised eMudhra intermediates. The rest of the stack was patched between Oct 20 and Oct 24 (livekit/rust-sdks#1546, livekit/rust-sdks#1549, livekit/rust-sdks#1562, livekit/python-sdks#881, livekit/python-sdks#891, #7998), but the plugin wasn't.
The plugin makes its own HTTPS request. On every room connect, livekit-ffi calls audio_filter_on_load({"url", "token"}). The plugin then sends GET https://<room host>/settings with the room token as Authorization: Bearer, through its bundled ureq + rustls stack.
That request verifies against a root store compiled into liblivekit_nc_plugin.so, not the system store or certifi:
| 0.2.5 | 0.3.2 | |
|---|---|---|
| rustls-webpki | 0.103.3 | 0.103.15 |
| emSign roots compiled in | C1, C3, G1, ECC G3 | C1, C3, G1, ECC G3 |
rustls-webpki 0.103.16 adds the distrusted-SPKI list (rustls/webpki#546), and webpki-roots 1.0.10 drops the affected roots. Neither is in any plugin release yet. Upgrading livekit, certifi or the OS ca-certificates doesn't affect this request, so users of BVC / NC / BVCTelephony can't fix it on their side.
Expected Behavior
The plugin's /settings request rejects certificate paths through the compromised eMudhra intermediates, as livekit-ffi 0.13.1+ already does (rustls-webpki >= 0.103.16, webpki-roots >= 1.0.10).
Reproduction Steps
pip download --no-deps --only-binary=:all: --platform manylinux_2_28_x86_64 --python-version 3.13 livekit-plugins-noise-cancellation==0.3.2
unzip -q livekit_plugins_noise_cancellation-0.3.2-*.whl
SO=livekit/plugins/noise_cancellation/resources/liblivekit_nc_plugin.so
# 1. Bundled TLS stack and compiled-in emSign roots
strings -n 6 $SO | grep -oE '(rustls|rustls-webpki|ureq)-[0-9.]+' | sort -u # rustls-0.23.45 rustls-webpki-0.103.15 ureq-3.4.2
strings -n 6 $SO | grep -E 'emSign .*Root CA' | sort -u # C1, C3, G1, ECC G3
# 2. The plugin opens its own TLS connection on on_load
python3 - <<'EOF'
import ctypes, json, time
lib = ctypes.CDLL("livekit/plugins/noise_cancellation/resources/liblivekit_nc_plugin.so")
lib.audio_filter_on_load(json.dumps({"url": "wss://example.com", "token": "dummy"}).encode())
time.sleep(5) # RUST_LOG=debug: ureq completes TLS to example.com and gets 404
EOF
# Same call with url ws://127.0.0.1:<port> against a plain HTTP server logs: GET /settings, Authorization: Bearer <token>
# 3. It ignores the system trust store: a private CA added to /etc/ssl/certs (or SSL_CERT_FILE)
# is still rejected with "invalid peer certificate: UnknownIssuer", and strace shows no reads under /etc/ssl.Operating System
Linux x86_64 (Debian bookworm, python:3.13-slim), LiveKit Cloud agents
Models Used
No response
Package Versions
livekit==1.2.0
livekit-agents==1.3.6
livekit-plugins-noise-cancellation==0.2.5 (0.3.2 checked too, same result)Session/Room/Call IDs
No response
Proposed Solution
# Rebuild liblivekit_nc_plugin with the same bump as livekit/rust-sdks#1546:
# cargo update -p rustls-webpki -p webpki-roots -p webpki-root-certs
# (rustls-webpki >= 0.103.16, webpki-roots / webpki-root-certs >= 1.0.10)
# and publish a new livekit-plugins-noise-cancellation (and the Node package, if it ships the same library).Additional Context
Exposure is narrow but real. An attacker would need a network position between the agent and the LiveKit Cloud host, plus a certificate issued by one of the compromised intermediates. With that, they could capture the room token sent to /settings, or forge the settings response to turn noise cancellation off.
Could you share an ETA for a patched release? We'd like to close this item in our eMudhra remediation.
Screenshots and Recordings
No response
Activity