Skip to content
Fencer Vulns
low 2.6

CVE-2005-0626 json

Race condition in Squid 2.5.STABLE7 to 2.5.STABLE9, when using the Netscape Set-Cookie recommendations for handling cookies in caches, may…

published 2005-03-03 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0627

cvss
2.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

Race condition in Squid 2.5.STABLE7 to 2.5.STABLE9, when using the Netscape Set-Cookie recommendations for handling cookies in caches, may cause Set-Cookie headers to be sent to other users, which allows attackers to steal the related cookies.

Patch / fix

  • squid Debian 14, Debian 13, Debian 12 2.5.9-2

debian advisories DEBIAN-CVE-2005-0626

  • squid RHEL 3 7:2.5.STABLE3-6.3E.13
  • squid RHEL 4 7:2.5.STABLE6-3.4E.9

red hat advisories RHSA-2005:415

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-0626 updated

security flaw

  • Red Hat Desktop version 3 squid 2.5.STABLE3-6.3E.13 Red Hat Enterprise Linux AS version 3 squid 2.5.STABLE3-6.3E.13 Red Hat Enterprise Linux AS version 4 squid 2.5.STABLE6-3.4E.9 Red Hat Enterprise Linux Desktop version 4 squid 2.5.STABLE6-3.4E.9 Red Hat Enterprise Linux ES version 3 squid 2.5.STABLE3-6.3E.13 Red Hat Enterprise Linux ES version 4 squid 2.5.STABLE6-3.4E.9
    +2 more products
    Red Hat Enterprise Linux WS version 3 squid 2.5.STABLE3-6.3E.13 Red Hat Enterprise Linux WS version 4 squid 2.5.STABLE6-3.4E.9
    fixed: vendor fix RHSA-2005:415

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.