CVE-2026-6722

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 43% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 24, 2026

Advisory Details (11)

Auto-updated Aug 21, 2026
Patch available. Sources: github, redhat.
redhat Patch Available

2468560 – (CVE-2026-6722) CVE-2026-6722 php: php-soap: php-src: PHP SOAP extension: Remote Code Execution via use-after-free vulnerability

Affected: Red Hat Enterprise Linux 9

https://bugzilla.redhat.com/show_bug.cgi?id=2468560
redhat Patch Available

CVE-2026-6722 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-6722
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:34354
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33449
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:23388
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:22649
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:22305
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:22143
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:22142
github Patch Available

Use-After-Free in SOAP using Apache map with Remote Code Execution · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-85c2-q967-79q5
redhat

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-6722.json

Vendor Advisories for CVE-2026-6722(8)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp8.4-zip (8.4.11-1ubuntu1.2) @ questing2026-08-23ubuntu
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm19) @ xenial2026-08-23ubuntu
redhatphp:7.4-8100020260604072603.f79986652026-07-01redhat
redhatphp-0:8.0.30-6.el9_82026-06-30redhat
redhatphp-0:8.3.31-1.el10_22026-06-04redhat
redhatphp8.4-0:8.4.21-1.el10_22026-06-02redhat
redhatphp:8.3-9080020260521113736.92026-06-01redhat
redhatphp:8.2-9080020260521080715.92026-06-01redhat
redhatphp:8.2-8100020260521052503.f79986652026-06-01redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
php7.47.4.21-1+deb11u1 ... 7.4.33-1+deb11u9 (14 versions)7.4.33-1+deb11u11—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (26 versions)8.2.31-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-18.4.21-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1, 8.4.16-1, 8.4.16-1~deb13u1, 8.4.20-1, 8.4.21-1~deb13u18.4.21-1—

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 7× in last 7d / 95× 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 270 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6722?
CVE-2026-6722 is a critical vulnerability published on May 10, 2026. In PHP versions 8.2. before 8.2.31, 8.3. before 8.3.31, 8.4. before 8.4.21, and 8.5. before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys,…
When was CVE-2026-6722 disclosed?
CVE-2026-6722 was first published in the National Vulnerability Database on May 10, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6722 actively exploited?
CVE-2026-6722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.2% of all scored CVEs.
What is the CVSS score of CVE-2026-6722?
CVE-2026-6722 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-6722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6722, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6722

Explore →

Is Your Infrastructure Affected by CVE-2026-6722?

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

Start Free Scan →Browse All CVEs