CVE-2026-7568

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 85% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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 metaphone() function in ext/standard/metaphone.c uses a signed int variable to track the current position within the input string. If a string longer than 2,147,483,647 bytes is passed, a signed integer overflow occurs, resulting in undefined behavior. This can lead to an out-of-bounds read, causing a segmentation fault or access to unrelated memory, and may affect the availability of the PHP process.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
36.4%
KEV
Not listed

Published

May 10, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated May 10, 2026
Patch available. Sources: github.
github Patch Available

Signed integer overflow in metaphone() · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-96wq-48vp-hh57

Vendor Advisories for CVE-2026-7568(8)

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 / EcosystemFixed in / PatchReleasedSource
ubuntuphp8.4-zip (8.4.11-1ubuntu1.2) @ questing2026-06-28ubuntu
redhatphp-0:8.3.31-1.el10_22026-06-04redhat
redhatphp8.4-0:8.4.21-1.el10_22026-06-02redhat
redhatphp:8.2-8100020260521052503.f79986652026-06-01redhat
redhatphp:8.3-9080020260521113736.92026-06-01redhat
redhatphp:8.2-9080020260521080715.92026-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.

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 10× in last 7d / 80× 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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-7568?
CVE-2026-7568 is a high 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 metaphone() function in ext/standard/metaphone.c uses a signed int variable to track the current position within the input string. If a string longer than 2,147,483,647 bytes is passed, a signed…
When was CVE-2026-7568 disclosed?
CVE-2026-7568 was first published in the National Vulnerability Database on May 10, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7568 actively exploited?
CVE-2026-7568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7568?
CVE-2026-7568 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7568, 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

Explore the affected products and dependency analysis for CVE-2026-7568

Explore →

Is Your Infrastructure Affected by CVE-2026-7568?

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

Start Free Scan →Browse All CVEs