CVE-2024-2756 | __Host-/__Secure- cookie bypass due to partial CVE-2022-31629 fix

Due to an incomplete fix to CVE-2022-31629 https://github.com/advisories/GHSA-c43m-486j-j32p , network and same-site attackers can set a standard insecure cookie in the victim's browser which is treated as a __Host- or __Secure- cookie by PHP applications.

Published: 2024-04-29 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-2756 is rated Moderate Risk (59.3/100): CVSS Medium severity, with high exploitation likelihood (EPSS 8.70%, 93th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-2756

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-18 7.75% 8.70% +0.95%
2 2026-02-13 9.76% 7.75% -2.02%
3 2026-01-18 — 9.76% —

Full EPSS history (31 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-2756

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2024-2756

OS Trackers for CVE-2024-2756

vendor priority summary link
alpine — CVE-2024-2756: 3 source package rows (php81, php82, php83); 12 state rows across 5 repos (3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 12, open 0. https://security.alpinelinux.org/vuln/CVE-2024-2756
debian not yet assigned CVE-2024-2756 not yet assigned priority: Debian including 2 source packages (php7.4, php8.2), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2024-2756
gentoo high CVE-2024-2756: 1 GLSA(s) (202408-32), 1 atom(s) (dev-lang/php); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-2756
redhat medium — https://access.redhat.com/security/cve/CVE-2024-2756
suse medium CVE-2024-2756 severity moderate: SUSE including 509 source package names (apache2-mod_php7, apache2-mod_php7-7.4.33-150200.3.65.1, …), 1206 product×package rows across 28 product lines (Container bci/php, Container bci/php-apache, … (28 product lines)): Fixed 987, Known Not Affected 219. https://www.suse.com/security/cve/CVE-2024-2756/
ubuntu medium CVE-2024-2756 medium priority: Ubuntu including 7 source packages (php5, php7.0, …), 65 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 50, released 10, needs-triage 5. https://ubuntu.com/security/CVE-2024-2756

Affected software / configurations for CVE-2024-2756

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-2756

cvelogic Threat Intelligence