Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | deferred | 2026-03-11 |
| esm-apps/resolute | deferred | 2026-03-11 |
| esm-infra-legacy/xenial | deferred | 2026-03-11 |
| esm-infra/bionic | deferred | 2026-03-11 |
| esm-infra/focal | deferred | 2026-03-11 |
| esm-infra/xenial | ignored | end of ESM support, was deferred [2026-03-11] |
| jammy | deferred | 2026-03-11 |
| noble | deferred | 2026-03-11 |
| plucky | ignored | end of life, was deferred [2026-03-11] |
| questing | ignored | end of life, was deferred [2026-03-11] |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | deferred | 2026-03-11 |
| esm-apps/jammy | deferred | 2026-03-11 |
| jammy | deferred | 2026-03-11 |
| noble | deferred | 2026-03-11 |
| plucky | ignored | end of life, was deferred [2026-03-11] |
| questing | ignored | end of life, was deferred [2026-03-11] |
| resolute | deferred | 2026-03-11 |
| upstream | needed |
Показывать по
5.9 Medium
CVSS3
Связанные уязвимости
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.
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.
A flaw was found in libsoup\u2019s caching mechanism, SoupCache, where ...
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.
5.9 Medium
CVSS3