SoupCache ignores the HTTP Vary header when reusing cached responses. The
vulnerable path is only reachable when a client explicitly enables the optional
on-disk SoupCache feature (soup_session_add_feature with SoupCache) AND acts as a
shared/multi-user HTTP proxy — neither applies to Echo's use of libsoup3 as a
client library. No upstream fix exists (a TODO in soup_cache_has_response();
issue #453 was closed as a duplicate of the still-open upstream issue #112).
Debian rates it no-dsa, Minor.
https://security-tracker.debian.org/tracker/CVE-2025-9901