Repository navigation
CookieRadar 2026.44
Security
CVE-2026-95210,CVE-2026-95209,CVE-2026-95184,CVE-2026-67693(gnutls28) and
CVE-2026-107778(krb5) recorded inSECURITY-EXCEPTIONS.toml. Docker Scout opened
the five against 2026.43 on 2026-10-09, one of them critical;patchradar debianthe
same day says open in trixie, no fix in any suite, no Debian bug, and the tracker still
asks whether the four gnutls reports are valid. Neither library is in the base image:
playwright install-deps chromiumbrings them in for libcups2t64, which is the only
package depending on them. Measured in the published image, Playwright's fullchrome
links cups and so loads both; thechrome-headless-shellthat cookieradar runs — the
only mode that works in an image with no display — maps none of gnutls, krb5 or cups.
No TLS here goes through gnutls (httpx uses OpenSSL via_ssl, Chromium its BoringSSL)
and nothing uses Kerberos. Reviewed with the other Chromium dependencies by 2026-11-30.
Fixed
-
The report says when it was made and by what. The README calls it "evidence of
what the site did on a given day", and the file saved on 2026-10-09 for
www.repubblica.it carried no day: the only dates in it were the "Version of:" lines
under the legal citations, which exist only when something is cited, and nothing
named the CookieRadar that produced it. Every report now opens with
Audited on 2026-10-09 12:37 UTC with CookieRadar 2026.43, and the HTML file has a
<title>with the site's host — Rich's export template has none, so ten reports
open side by side were ten tabs calledreport.html. -
The law section no longer says "no cookie banner was found" under a report that
says "Banner found". Measured on 2026-10-09 on it.wikipedia.org, www.subito.it and
www.muenchen.de: every session printed the tick, neither button was clicked, and the
UNVERIFIED note denied the banner. Both lines came from one result. The heuristic
cannot tell a Didomi notice from a footer link called "Dichiarazione sui cookie"
(Wikipedia's match), and the note now says what it knows: something that looks like
a banner was found, and no refusal control was recognised on it. -
A page that never goes idle keeps its HTTP status.
page.goto(wait_until= "networkidle")returns the response only when the wait succeeds; when the page keeps
the network busy it raises a timeout and the status, which had arrived in the first
second, was lost with it. Measured on 2026-10-09: zalando.it answered 403 from its
edge with a full page whose scripts never went quiet, so the status was None,
page_not_servedsaw nothing wrong, and the audit said "0 trackers before consent,
UNVERIFIED" about an error page it never had; enel.it and poste.it, served with 200
and never idle, showed no status in any session. The status is now taken from the
main document's response as it arrives, last hop of a redirect, andgotoonly
confirms it.tests/site/forbidden_busy.html, served with 403 by the test server
under/forbidden/, reproduces the zalando.it case. -
TrustArc and Usercentrics refusals are clicked, and so are "Non accetto",
"Continua senza accettare" and "Solo gli essenziali". Measured on 2026-10-09:
enel.it and poste.it (TrustArc) offer refusal in one click —#truste-consent-required
"Continua senza accettare", whose banner says it leaves only technical cookies, and
#truste-consent-required2"Non accetto" — and the audit clicked "Accetta", found no
refusal, and reported "Accept was applied and no refusal control was found" with
GDPR art. 4(11) cited against both. zalando.it (Usercentrics) renders its banner in a
shadow root with no ids; the refusal is[data-testid="uc-deny-all-button"]"Solo gli
essenziali". The three banners are intests/site/, captured from the real pages
that day, and the sessions now click the refusal on each and the acceptance on none. -
An error page in any of the three sessions means NOT MEASURED.
page_not_served
read the pre-consent status only. In the batch run of 2026-10-09 www.zalando.it got no
response at all in the pre-consent session and the edge's 403 page in the post-reject
one — with a Usercentrics banner over it and Google Tag Manager loading once "Solo gli
essenziali" was clicked — and the verdict came out as VIOLATION, 2 trackers new after
rejection, assembled from one session that saw nothing and one that saw an error page.
The verdict rests on session 3; an error page there leaves it nothing to rest on. The
report now names the session that got the error page, and the other sessions' tables
say that no verdict rests on them.
Changed
- The test matrix runs on
3.15-devtoo, as an experimental row. 3.15.0 final is
due 2026-10-09 (PEP 790) and the dependencies the suite stands on already ship
cp315 wheels;actions/setup-pythonresolves3.15-devto the newest build, rc.3
today and the final once it is out. The row is anincludewith
continue-on-error, so it may fail without failing the run or the required
Testscheck; the classifiers still stop at 3.14 until 3.15 is final. patchradar
has had the same row since 2026-08-20.