How severe is GHSA-gm98-g2wf-7c68?

No CVSS score has been assigned to GHSA-gm98-g2wf-7c68 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gm98-g2wf-7c68?

GHSA-gm98-g2wf-7c68 affects the following packages: amphp/artax (Packagist), amphp/artax (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gm98-g2wf-7c68?

Update amphp/artax to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm98-g2wf-7c68 is resolved across your whole dependency graph.

How do I detect GHSA-gm98-g2wf-7c68 in my Packagist dependencies?

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

How do I mitigate GHSA-gm98-g2wf-7c68 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gm98-g2wf-7c68?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gm98-g2wf-7c68 can be triaged on real exposure rather than presence alone.

Is GHSA-gm98-g2wf-7c68 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gm98-g2wf-7c68 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.

When was GHSA-gm98-g2wf-7c68 published, and has it been updated?

GHSA-gm98-g2wf-7c68 was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-gm98-g2wf-7c68 — amphp/artax

Fix: amphp/artax@25668b8

GHSA-gm98-g2wf-7c68 is a security vulnerability in amphp/artax. A fix is available for amphp/artax — see the affected versions and patch details below.

amphp/artax Cookie leakage to wrong origins and non-restricted cookie acceptance

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘amphp/artax🐘amphp/artax

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

Description

In artax version before 1.0.6 and 2 before 2.0.6, cookies of foo.bar.example.com were leaked to foo.bar. Additionally, any site could set cookies for any other site. Artax fixed this issue by following newer browser implementations now. Cookies can only be set on domains higher or equal to the current domain, but not on any public suffixes.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`amphp/artax`	≥ 2&&< 2.0.6	2.0.6`composer require amphp/artax:^2.0.6`
🐘Packagist	`amphp/artax`	all versions	1.0.6`composer require amphp/artax:^1.0.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amphp/artax, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update amphp/artax to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm98-g2wf-7c68 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gm98-g2wf-7c68 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-gm98-g2wf-7c68. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In artax version before 1.0.6 and 2 before 2.0.6, cookies of `foo.bar.example.com` were leaked to `foo.bar`. Additionally, any site could set cookies for any other site. Artax fixed this issue by following newer browser implementations now. Cookies can only be set on domains higher or equal to the current domain, but not on any public suffixes.

O3 Security · Impact-Aware SCA

Is GHSA-gm98-g2wf-7c68 in your dependencies?

O3 Security finds GHSA-gm98-g2wf-7c68 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works