CVE-2022-31629

HIGHNVD 6.57.4▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.4 because EPSS predicts 49% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
7.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 49%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the vulnerability enables network and same-site attackers to set a standard insecure cookie in the victim's browser which is treated as a __Host- or __Secure- cookie by PHP applications.

CVSS v3
6.5
EG Score
7.4HIGHhigh confidence
EG Risk
53
EG Risk 53/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation49% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
49%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2022

Last Modified

November 4, 2025

References (26)

Vendor Advisories for CVE-2022-31629(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp8.1-snmp (8.1.7-1ubuntu3.1) @ kinetic2026-05-25ubuntu
ubuntuphp7.0-snmp (7.0.33-0ubuntu0.16.04.16+esm5) @ xenial2026-05-25ubuntu
redhatphp:7.4-8080020230118140634.cc3424242023-05-16redhat
redhatphp:8.1-9020020230120141750.92023-05-09redhat
redhatphp-0:8.0.27-1.el9_12023-02-28redhat
redhatphp:8.0-8070020230118114629.ef3316622023-02-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
php7.37.3.10-1 ... 7.3.9-1~deb10u1 (16 versions)
  • every version up to 7.3.31-1~deb10u2: fixed in 7.3.31-1~deb10u2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
php7.47.4.21-1+deb11u1, 7.4.25-1+deb11u1, 7.4.26-1, 7.4.28-1+deb11u1, 7.4.30-1+deb11u1
  • every version up to 7.4.33-1+deb11u1: fixed in 7.4.33-1+deb11u1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 160 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:40 UTCEPSS rescore
  3. 2026-10-07 23:45 UTCEPSS rescore
  4. 2026-10-06 15:14 UTCEPSS rescore
  5. 2026-10-03 14:23 UTCEPSS rescore
  6. 2026-10-02 16:23 UTCEPSS rescore
  7. 2026-09-30 15:55 UTCEG score recompute
  8. 2026-09-30 15:00 UTCEPSS rescore
  9. 2026-09-27 13:42 UTCEPSS rescore
  10. 2026-09-26 15:54 UTCEPSS rescore
  11. 2026-09-24 14:00 UTCEPSS rescore
  12. 2026-09-24 10:26 UTCOSV refresh
  13. 2026-09-23 13:45 UTCEPSS rescore
  14. 2026-09-22 14:44 UTCEPSS rescore
  15. 2026-09-20 20:13 UTCEPSS rescore
  16. 2026-09-19 15:38 UTCEPSS rescore
  17. 2026-09-18 19:24 UTCEPSS rescore
  18. 2026-09-16 14:05 UTCEPSS rescore
  19. 2026-09-15 03:06 UTCEPSS rescore
  20. 2026-09-12 14:57 UTCEPSS rescore
  21. 2026-09-11 14:49 UTCEPSS rescore
  22. 2026-09-11 09:33 UTCEPSS rescore
  23. 2026-09-08 21:57 UTCEPSS rescore
  24. 2026-09-06 13:45 UTCEPSS rescore
  25. 2026-09-05 15:25 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 02:48 UTCOSV refresh
  2. 2026-09-04 13:57 UTCEPSS rescore
  3. 2026-09-04 13:57 UTCEPSS rescore
  4. 2026-09-02 14:09 UTCEPSS rescore
  5. 2026-09-01 13:51 UTCEPSS rescore
  6. 2026-08-30 19:14 UTCEPSS rescore
  7. 2026-08-30 01:19 UTCEPSS rescore
  8. 2026-08-28 21:38 UTCEPSS rescore
  9. 2026-08-27 14:22 UTCEPSS rescore
  10. 2026-08-26 14:43 UTCEPSS rescore
  11. 2026-08-25 13:46 UTCEPSS rescore
  12. 2026-08-24 14:13 UTCEPSS rescore
  13. 2026-08-23 00:16 UTCEPSS rescore
  14. 2026-08-21 23:46 UTCEPSS rescore
  15. 2026-08-20 22:52 UTCEPSS rescore
  16. 2026-08-19 17:01 UTCEPSS rescore
  17. 2026-08-18 14:10 UTCOSV refresh
  18. 2026-08-18 13:45 UTCEPSS rescore
  19. 2026-08-17 13:44 UTCEPSS rescore
  20. 2026-08-16 02:11 UTCEPSS rescore
  21. 2026-08-15 01:27 UTCEPSS rescore
  22. 2026-08-12 13:48 UTCEPSS rescore
  23. 2026-08-11 13:38 UTCEPSS rescore
  24. 2026-08-09 13:44 UTCEPSS rescore
  25. 2026-08-07 16:24 UTCEPSS rescore
  26. 2026-08-06 13:44 UTCEPSS rescore
  27. 2026-08-05 19:15 UTCEPSS rescore
  28. 2026-08-03 10:33 UTCEPSS rescore
  29. 2026-08-03 09:27 UTCOSV refresh
  30. 2026-08-02 02:24 UTCEPSS rescore
  31. 2026-07-30 16:25 UTCEPSS rescore
  32. 2026-07-30 01:28 UTCEPSS rescore
  33. 2026-07-28 15:33 UTCEPSS rescore
  34. 2026-07-26 14:52 UTCEPSS rescore
  35. 2026-07-25 14:15 UTCEPSS rescore
  36. 2026-07-24 14:15 UTCEPSS rescore
  37. 2026-07-24 14:15 UTCEPSS rescore
  38. 2026-07-23 14:16 UTCEPSS rescore
  39. 2026-07-23 14:16 UTCEPSS rescore
  40. 2026-07-23 02:11 UTCEG score recompute▲ 0.90
  41. 2026-07-22 22:58 UTCEG score recompute
  42. 2026-07-22 14:06 UTCEPSS rescore
  43. 2026-07-22 14:06 UTCEPSS rescore
  44. 2026-07-21 15:22 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-20 17:05 UTCEPSS rescore
  47. 2026-07-19 02:27 UTCEPSS rescore
  48. 2026-07-19 02:27 UTCEPSS rescore
  49. 2026-07-16 18:53 UTCOSV refresh
  50. 2026-07-16 17:00 UTCEPSS rescore
  51. 2026-07-15 16:56 UTCEPSS rescore
  52. 2026-07-15 16:56 UTCEPSS rescore
  53. 2026-07-15 01:58 UTCEPSS rescore
  54. 2026-07-15 01:58 UTCEPSS rescore
  55. 2026-07-13 22:27 UTCEPSS rescore
  56. 2026-07-13 06:11 UTCEPSS rescore
  57. 2026-07-13 06:11 UTCEPSS rescore
  58. 2026-07-12 05:44 UTCEPSS rescore
  59. 2026-07-12 05:44 UTCEPSS rescore
  60. 2026-07-11 08:25 UTCEPSS rescore
  61. 2026-07-11 08:25 UTCEPSS rescore
  62. 2026-07-09 19:07 UTCEPSS rescore
  63. 2026-07-07 13:44 UTCEPSS rescore
  64. 2026-07-05 02:28 UTCEPSS rescore
  65. 2026-07-05 02:28 UTCEPSS rescore
  66. 2026-07-01 15:04 UTCEPSS rescore
  67. 2026-06-30 23:20 UTCEPSS rescore
  68. 2026-06-30 23:20 UTCEPSS rescore
  69. 2026-06-29 14:04 UTCEPSS rescore
  70. 2026-06-28 17:32 UTCOSV refresh
  71. 2026-06-28 04:54 UTCEPSS rescore
  72. 2026-06-25 13:48 UTCEPSS rescore
  73. 2026-06-25 13:48 UTCEPSS rescore
  74. 2026-06-24 14:03 UTCEPSS rescore
  75. 2026-06-24 14:03 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsilnex/CVE-2022-31629-poc
    First seen Oct 7, 2022

    CVE-2022-31629 POC

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-31629?
CVE-2022-31629 is a high vulnerability published on September 28, 2022. In PHP versions before 7.4.31, 8.0.24 and 8.1.11, the vulnerability enables network and same-site attackers to set a standard insecure cookie in the victim's browser which is treated as a Host- or Secure- cookie by PHP applications.
When was CVE-2022-31629 disclosed?
CVE-2022-31629 was first published on September 28, 2022, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-31629 actively exploited?
CVE-2022-31629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-31629?
CVE-2022-31629 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4 (HIGH).
How do I remediate CVE-2022-31629?
A fix for CVE-2022-31629 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-31629 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31629

Explore →

Is Your Infrastructure Affected by CVE-2022-31629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs