How severe is GHSA-pr33-38xx-6r26?

No CVSS score has been assigned to GHSA-pr33-38xx-6r26 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pr33-38xx-6r26?

GHSA-pr33-38xx-6r26 affects the following packages: org.http4k:http4k-core (Maven), org.http4k:http4k-core (Maven), org.http4k:http4k-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pr33-38xx-6r26?

Update org.http4k:http4k-core to 6.48.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr33-38xx-6r26 is resolved across your whole dependency graph.

How do I detect GHSA-pr33-38xx-6r26 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.http4k:http4k-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pr33-38xx-6r26 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-pr33-38xx-6r26 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pr33-38xx-6r26 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pr33-38xx-6r26?

GHSA-pr33-38xx-6r26 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pr33-38xx-6r26?

GHSA-pr33-38xx-6r26 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pr33-38xx-6r26 published, and has it been updated?

GHSA-pr33-38xx-6r26 was published on June 19, 2026 and was last updated on September 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

http4k: BasicCookieStorage` (renamed `InsecureCookieStorage`) did not enforce RFC 6265 cookie scoping; new `DefaultCookieStorage` is now the defaultGHSA-pr33-38xx-6r26

Fix: http4k/http4k@6a9b44d

GHSA-pr33-38xx-6r26 is a Information Exposure vulnerability in org.http4k:http4k-core. A fix is available for org.http4k:http4k-core — see the affected versions and patch details below.

Also known asCVE-2026-100725

Published

Jun 19, 2026

Updated

Sep 27, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pr33-38xx-6r26.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.http4k:http4k-core☕org.http4k:http4k-core☕org.http4k:http4k-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The previous BasicCookieStorage did not enforce RFC 6265 scoping rules around cookie domain, path, and Secure attribute. A client using a single storage instance to talk to multiple origins could have cookies leak across domains, or have Secure cookies sent over plain HTTP — the deprecation message states it bluntly: "BasicCookieStorage has no domain/path/scheme scoping and leaks cookies across origins. Use DefaultCookieStorage instead."

Who is affected: any client using BasicCookieStorage directly with cookies for more than one origin or scheme. Single-origin uses are unaffected.

Patches

Line	Fixed in	Edition
v6.x (Community)	6.48.0.0	Community
v5.x (LTS)	5.42.0.0	Enterprise — contact [email protected]
v4.x (LTS)	4.51.0.0	Enterprise — contact [email protected]

The fix introduces DefaultCookieStorage (RFC 6265 compliant) as the drop-in default; BasicCookieStorage is renamed InsecureCookieStorage and remains available for callers with a deliberate need for the old behaviour.

Workarounds

For deployments that cannot upgrade immediately:

Use a dedicated BasicCookieStorage instance per origin / scheme, or
Switch to a separate RFC 6265-compliant cookie store implementation.

References

Fix release: v6.48.0.0
Cookie storage rewrite: 6a9b44d743
Background: RFC 6265 — HTTP State Management Mechanism

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.http4k:http4k-core`	≥ 6.0.0.0&&< 6.48.0.0	6.48.0.0`org.http4k:http4k-core:6.48.0.0`
☕Maven	`org.http4k:http4k-core`	≥ 5.0.0.0&&< 5.42.0.0	5.42.0.0`org.http4k:http4k-core:5.42.0.0`
☕Maven	`org.http4k:http4k-core`	all versions	4.51.0.0`org.http4k:http4k-core:4.51.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.http4k:http4k-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.http4k:http4k-core to 6.48.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr33-38xx-6r26 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

http4k-core versions before 4.51.0.0, 5.42.0.0, and 6.48.0.0 do not enforce cookie domain, path, and Secure scoping. Applications sharing cookie storage across origins or schemes may disclose session tokens or credentials; single-origin storage is unaffected.

Workaround published by Red Hat

Upgrade to http4k-core 4.51.0.0, 5.42.0.0, 6.48.0.0, or later on the corresponding release branch. If upgrading is not possible, do not share BasicCookieStorage across origins or HTTP/HTTPS schemes; use separate storage per origin.

Source: Red Hat security advisory for GHSA-pr33-38xx-6r26 (CC BY 4.0)

Frequently Asked Questions

### Impact The previous `BasicCookieStorage` did not enforce RFC 6265 scoping rules around cookie domain, path, and `Secure` attribute. A client using a single storage instance to talk to multiple origins could have cookies leak across domains, or have `Secure` cookies sent over plain HTTP — the deprecation message states it bluntly: *"BasicCookieStorage has no domain/path/scheme scoping and leaks cookies across origins. Use DefaultCookieStorage instead."* **Who is affected:** any client using `BasicCookieStorage` directly with cookies for more than one origin or scheme. Single-origin uses a

O3 Security · Impact-Aware SCA

Is GHSA-pr33-38xx-6r26 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works