CVE-2026-7260

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% 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
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

Circular symbolic links in phar archives could lead to unbounded recursion, exhausting the C stack and crashing the PHP process, in PHP versions from 8.2.* before 8.2.33, from 8.3.* before 8.3.33, from 8.4.* before 8.4.24, and from 8.5.* before 8.5.9.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
Patch available. Sources: github.
github Patch Available

Stack overflow in phar with circular symlinks · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-vc5h-9ppw-p5f3

Vendor Advisories for CVE-2026-7260(1)

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
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm20) @ xenial2026-09-20ubuntu
ubuntuphp8.5-zip (8.5.4-0ubuntu1.3) @ resolute2026-09-20ubuntu
redhatphp-0:8.3.33-1.el10_22026-09-02redhat
redhatphp:7.4-8100020260805070257.f79986652026-09-01redhat
redhatphp:8.2-9080020260806120914.92026-09-01redhat
redhatphp-0:8.0.30-8.el9_82026-08-31redhat
redhatphp:8.2-8100020260806050858.f79986652026-08-20redhat
redhatphp:8.3-9080020260806131732.92026-08-20redhat
redhatphp-main-8.5.9-1.hum12026-07-28redhat

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 (15 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (28 versions)8.2.33-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1 ... 8.4.23-1~deb13u1 (9 versions)8.4.24-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1 ... 8.4.24-1~deb13u1 (10 versions)8.4.24-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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 17× in last 7d / 68× 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 126 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Same vendor

3 shown

redhat:RHSA-2026:47200 · redhat:RHSA-2026:61259

Frequently asked(5)

What is CVE-2026-7260?
CVE-2026-7260 is a medium vulnerability published on July 30, 2026. Circular symbolic links in phar archives could lead to unbounded recursion, exhausting the C stack and crashing the PHP process, in PHP versions from 8.2. before 8.2.33, from 8.3. before 8.3.33, from 8.4. before 8.4.24, and from 8.5. before 8.5.9.
When was CVE-2026-7260 disclosed?
CVE-2026-7260 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7260 actively exploited?
CVE-2026-7260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-7260?
CVE-2026-7260 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-7260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7260, 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-7260

Explore →

Is Your Infrastructure Affected by CVE-2026-7260?

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

Start Free Scan →Browse All CVEs