CVE-2026-17543

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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 — Patch released this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Improper escaping of backslashes in attacker-provided parameters would allow for trivial SQL injection 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
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/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%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 5, 2026

Advisory Details (1)

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

SQL injection in ext-pgsql via E'...' backslash breakout · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-7qpv-r5mr-78m4

Vendor Advisories for CVE-2026-17543(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatphp:8.2-8100020260806050858.f79986652026-08-20redhat
redhatphp:8.3-9080020260806131732.92026-08-20redhat
redhatphp8.4-0:8.4.24-1.el10_22026-08-19redhat
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)——
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 (11 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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

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

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 PoCHunt-Benito/e-is-for-exploit-cve-2026-17543-php-pgsql-sql-injection-backslash-breakout
    First seen Aug 6, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2026-17543?
CVE-2026-17543 is a critical vulnerability published on July 30, 2026. Improper escaping of backslashes in attacker-provided parameters would allow for trivial SQL injection 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-17543 disclosed?
CVE-2026-17543 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-17543 actively exploited?
CVE-2026-17543 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 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-17543?
CVE-2026-17543 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-17543?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17543, 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-17543

Explore →

Is Your Infrastructure Affected by CVE-2026-17543?

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

Start Free Scan →Browse All CVEs