medium CVSS 5.8

CVE-2026-55767·PHP vulnerability

Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, CookieJar incorrectly accepts cookies with a dot-only Domain attribute and whitespace-padded variants. SetCookie::matchesDomain() removes leading dots from the cookie domain, normalizing dot-only values to the empty string; SetCookie::validate() only rejected a strictly empty domain, so these cookies could be stored and the empty normalized domain was treated as matching any request host. An attacker-controlled origin that an application requests with a shared cookie jar can therefore set a cookie that Guzzle later sends to unrelated hosts using the same jar. This may allow cookie injection or session fixation against downstream services, depending on how those services interpret the injected cookie. This vulnerability is fixed in 7.12.1.

Severity
medium
Software
PHP
Fixed in
7.12.1
Published
2026-06-23

Affected versions

Until: 7.12.1

Fixed in: 7.12.1

How to fix this CVE

Update PHP and the Guzzle HTTP client library to version 7.12.1 or later to resolve this cookie handling vulnerability. The fix ensures that cookies with malformed domain attributes are properly rejected, preventing cookie injection attacks across unrelated hosts that share the same cookie jar.

sudo dnf update php php-curl

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed PHP version and Guzzle library: php -v && composer show guzzlehttp/guzzle
  2. Step 2: Verify Guzzle version is below 7.12.1 by examining vendor/guzzlehttp/guzzle/composer.json or running composer show guzzlehttp/guzzle | grep versions
  3. Step 3: Search application logs for Set-Cookie headers with empty or whitespace-padded Domain attributes using: grep -i 'Set-Cookie.*Domain=' /var/log/apache2/*.log /var/log/nginx/*.log | grep -E 'Domain=\s*$|Domain=\.+\s*$'
  4. Step 4: After updating, re-run composer show guzzlehttp/guzzle to confirm version is 7.12.1 or higher

FAQ

What is CVE-2026-55767?

CVE-2026-55767 is a cookie validation flaw in Guzzle's CookieJar that allows malformed domain attributes (empty or dot-only values) to be accepted and stored, enabling attackers to inject cookies that are sent to unrelated hosts when the same jar is reused across multiple requests.

Is CVE-2026-55767 being actively exploited?

No, CVE-2026-55767 is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available.

What versions of PHP are affected by CVE-2026-55767?

All versions of Guzzle below 7.12.1 are affected. The vulnerability exists in the CookieJar component, so any PHP application using Guzzle versions prior to 7.12.1 is at risk.

How do I check if my server is vulnerable to CVE-2026-55767?

Run 'composer show guzzlehttp/guzzle' in your application root directory. If the version shown is below 7.12.1, your application is vulnerable.

Does Defensia detect CVE-2026-55767?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP with Guzzle is installed on a monitored server, CVE-2026-55767 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.
CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-55767. Free for 1 server.

Get started free