Vulnerability in libsoup's caching mechanism (CVE-2025-9901)
Summary
Vulnerability in libsoup's caching mechanism (CVE-2025-9901). Confidential information can be exposed externally.
Original description
The description as published by the source.
A flaw was found in libsoup’s caching mechanism, SoupCache, where the HTTP Vary header is ignored when evaluating cached responses. This header ensures that responses vary appropriately based on request headers such as language or authentication. Without this check, cached content can be incorrectly reused across different requests, potentially exposing sensitive user information. While the issue is unlikely to affect everyday desktop use, it could result in confidentiality breaches in proxy or multi-user environments.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-9901 has been found in libsoup's caching mechanism.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "libsoup's caching mechanism CVE-2025-9901" on the vendor's site.
CVE-2025-9901 (libsoup's caching mechanism) — CWE-524 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-524) exists in libsoup's caching mechanism.
Check the vendor advisory for the affected versions of libsoup's caching mechanism.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで libsoup's caching mechanism を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-9901 libsoup2.4
- Ubuntu UBUNTU-CVE-2025-9901 libsoup2.4