CVE-2026-17543

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-51090 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Nov 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp7.0-zip (7.0.33-0ubuntu0.16.04.16+esm20) @ xenial2026-11-18ubuntu
ubuntuphp8.5-zip (8.5.4-0ubuntu1.3) @ resolute2026-11-18ubuntu
redhatphp-0:8.3.33-1.el10_22026-09-02redhat
redhatphp:8.2-9080020260806120914.92026-09-01redhat
redhatphp:7.4-8100020260805070257.f79986652026-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
redhatphp8.4-0:8.4.24-1.el10_22026-08-19redhat
redhatphp-main-8.5.9-1.hum12026-07-28redhat

These rows come from Ubuntu and Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(13 across 7 ecosystems)
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
php82—
  • every version up to 8.2.33-r0: fixed in 8.2.33-r0
—
php83—
  • every version up to 8.3.36-r0: fixed in 8.3.36-r0
—
php84—
  • every version up to 8.4.27-r0: fixed in 8.4.27-r0
—
Alpine:v3.23(3)
PackageVulnerable rangeFix by version rangeDependents
php83—
  • every version up to 8.3.36-r0: fixed in 8.3.36-r0
—
php84—
  • every version up to 8.4.27-r0: fixed in 8.4.27-r0
—
php85—
  • every version up to 8.5.12-r0: fixed in 8.5.12-r0
—
Alpine:v3.24(3)
PackageVulnerable rangeFix by version rangeDependents
php83—
  • every version up to 8.3.33-r0: fixed in 8.3.33-r0
—
php84—
  • every version up to 8.4.24-r0: fixed in 8.4.24-r0
—
php85—
  • every version up to 8.5.9-r0: fixed in 8.5.9-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
php7.47.4.21-1+deb11u1 ... 7.4.33-1+deb11u9 (15 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (28 versions)
  • every version up to 8.2.33-1~deb12u1: fixed in 8.2.33-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.23-1~deb13u1 (9 versions)
  • every version up to 8.4.24-1~deb13u1: fixed in 8.4.24-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.24-1~deb13u1 (10 versions)
  • every version up to 8.4.24-1: fixed in 8.4.24-1
—

Weakness Classification(1)

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 15× in last 7d / 62× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 472 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 372 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-17543?
CVE-2026-17543 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-17543 published?
The CVE record for CVE-2026-17543 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-17543 actively exploited?
CVE-2026-17543 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-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?
A fix for CVE-2026-17543 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17543 are linked in the Vendor Advisories panel on this page.

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.