CVE-2026-14355

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

In PHP versions 8.2.* before 8.2.32, 8.3.* before 8.3.32, 8.4.* before 8.4.23, 8.5.* before 8.5.8, the AES-WRAP-PAD algorithm implementation in OpenSSL extension contains a buffer allocation flaw. The output buffer for the AES key-wrap-with-padding operation is sized from the plaintext length without accounting for RFC 5649 expansion. This may cause OpenSSL to write beyond allocated memory, corrupting heap metadata and triggering application abort.

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

Published

July 3, 2026

Last Modified

July 8, 2026

Advisory Details (1)

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

ext/openssl: Memory corruption (zend_mm_heap corrupted) in openssl_encrypt with AES-WRAP-PAD · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-7jrw-539f-x6vr

Vendor Advisories for CVE-2026-14355(3)

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.5-zip (8.5.4-0ubuntu1.2) @ resolute2026-09-18ubuntu
redhatphp-0:8.0.30-8.el9_82026-08-31redhat
redhatphp8.4-0:8.4.23-1.el10_22026-08-04redhat
redhatphp:8.3-9080020260709051146.92026-07-31redhat
redhatphp:8.2-8100020260710044340.f79986652026-07-30redhat
redhatphp:7.4-8100020260710051855.f79986652026-07-30redhat
redhatphp-0:8.3.32-1.el10_22026-07-29redhat
redhatphp:8.2-9080020260709074538.92026-07-16redhat
redhatphp-main-8.5.8-2.hum12026-07-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 (15 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (27 versions)8.2.32-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1 ... 8.4.22-1 (7 versions)8.4.23-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
php8.48.4.11-1 ... 8.4.23-1~deb13u1 (8 versions)8.4.23-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

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 / 42× 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 139 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2026:61259

Frequently asked(5)

What is CVE-2026-14355?
CVE-2026-14355 is a medium vulnerability published on July 3, 2026. In PHP versions 8.2. before 8.2.32, 8.3. before 8.3.32, 8.4. before 8.4.23, 8.5. before 8.5.8, the AES-WRAP-PAD algorithm implementation in OpenSSL extension contains a buffer allocation flaw. The output buffer for the AES key-wrap-with-padding operation is sized from the plaintext length without…
When was CVE-2026-14355 disclosed?
CVE-2026-14355 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14355 actively exploited?
CVE-2026-14355 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 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-14355?
CVE-2026-14355 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-14355?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14355, 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-14355

Explore →

Is Your Infrastructure Affected by CVE-2026-14355?

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

Start Free Scan →Browse All CVEs