CVE-2026-1707

HIGHNVD 6.37.4
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-02-05. NVD baseline CVSS 6.3; sources differ by 1.1.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-5528 (ENISA EUVD) · GHSA-3p7x-94q9-jq9x (GitHub Security Advisories) · PYSEC-2026-2864 (OSV.dev)Source: ENISA EUVD

7.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pgAdmin versions 9.11 are affected by a Restore restriction bypass via key disclosure vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. An attacker with access to the pgAdmin web interface can observe an active restore operation, extract the \restrict key in real time, and race the restore process by overwriting the restore script with a payload that re-enables meta-commands using \unrestrict . This results in reliable command execution on the pgAdmin host during the restore operation.

CVSS v3
6.3
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
38th
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

February 5, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available.
Web page

Mask the secret key for restrict option in the process watcher when restoring plain SQL file. · Issue #9518 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/9518

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pippgadmin4 @ 9.12 (fixes < 9.12)—ghsa

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pgadmin44.20 ... 9.9 (74 versions)
  • every version up to 9.12: fixed in 9.12
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 193 refreshes 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 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-11-01 07:58 UTCGHSA enrichmentGHSA-3p7x-94q9-jq9x · GitHub severity HIGH · GitHub CVSS 7.4
  4. 2026-11-01 07:58 UTCEG score recompute▲ 1.10
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  6. 2026-10-31 07:25 UTCOSV refresh
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  13. 2026-10-25 14:46 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-23 06:18 UTCEG score recompute
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-18 04:00 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 75 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-12 16:29 UTCEG score recompute
  5. 2026-10-11 20:08 UTCEG score recompute
  6. 2026-10-11 17:21 UTCEG score recompute
  7. 2026-10-11 14:53 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-08 17:04 UTCOSV refresh
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-09-18 23:23 UTCOSV refresh
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  41. 2026-08-31 02:33 UTCOSV refresh
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  45. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  46. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  47. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  57. 2026-08-14 11:05 UTCEG score recompute
  58. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-08-13 03:24 UTCEG score recompute
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-08-09 15:44 UTCEG score recompute
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-08-07 22:42 UTCEG score recompute
  67. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  68. 2026-08-06 04:19 UTCEG score recompute
  69. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  70. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  71. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  72. 2026-08-02 21:21 UTCEG score recompute▼ 1.10
  73. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  74. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  75. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-1707?
CVE-2026-1707 is a high-severity vulnerability; its CVE record was published on February 5, 2026. pgAdmin versions 9.11 are affected by a Restore restriction bypass via key disclosure vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. An attacker with access to the pgAdmin web interface can observe an active restore operation, extract the…
When was CVE-2026-1707 made public?
CVE-2026-1707 was made public on January 30, 2026: that is the date its CVE record's CNA, PostgreSQL, gives for when the vulnerability was made public. The CVE record itself was published on February 5, 2026. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-1707 actively exploited?
CVE-2026-1707 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1707?
CVE-2026-1707 has a CVSS v3 base score of 6.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 7.4 (HIGH).
How do I remediate CVE-2026-1707?
A fix for CVE-2026-1707 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1707

Explore →

Is Your Infrastructure Affected by CVE-2026-1707?

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

Book a Demo →Browse All CVEs