Advisory record · GHSA-pr33-38xx-6r26

http4k: BasicCookieStorage` (renamed `InsecureCookieStorage`) did not enforce RFC 6265 cookie scoping; new `DefaultCookieStorage` is now the default

CVSS 8.3 HighEPSS 0.0024 · 15th percentile

Published by the GitHub Advisory Database at 19 Jun 2026, 21:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.http4k:http4k-coreMaven>=6.0.0.0, <6.48.0.0 || >=5.0.0.0, <5.42.0.0 || <4.51.0.06.48.0.0, 5.42.0.0, 4.51.0.0
Identifiers
GHSA-pr33-38xx-6r26 · CVE-2026-100725
Weakness (CWE)
CWE-200
Published
19 Jun 2026
Updated
27 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The http4k-core library is vulnerable in versions from 6.0.0.0 up to 6.48.0.0, from 5.0.0.0 up to 5.42.0.0, and below 4.51.0.0. The old BasicCookieStorage class did not enforce RFC 6265 domain, path, and Secure rules, so a client using one instance across multiple origins or schemes could leak cookies between them or send Secure cookies over plain HTTP. Upgrade to 6.48.0.0, 5.42.0.0, or 4.51.0.0; the fix adds DefaultCookieStorage as the default, and the old class is renamed InsecureCookieStorage. Single-origin use is not affected.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0024, the 15th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.