CVE-2026-86861

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-09-17. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

pgAdmin 4's File Manager save_file endpoint, which backs saving from the Query Tool and ERD, validated the requested path with Filemanager.check_access_permission() and then opened the file for writing with a plain open() call. CVE-2026-7819 had previously hardened the separate file upload path by opening its target with O_NOFOLLOW, so that the kernel refuses to follow a symbolic link at the final path component, but save_file was left on an unprotected open(). A symbolic link already present when the check ran was rejected by the check itself; the remaining exposure was a link substituted at the final path component in the interval between the check and the write, at which point the write followed the link and landed outside the user's storage directory, creating or overwriting an arbitrary file as the operating-system account running pgAdmin.

Exploitation requires the ability to create or replace a symbolic link inside the requesting user's storage directory. pgAdmin exposes no interface that creates symbolic links, so this requires filesystem access to the pgAdmin host or to a shared or network-mounted storage backend, together with winning the timing window. The reporter did not achieve a write against a released version, having attempted approximately 63,000 racing requests without success; the reported defect is the uncovered write path rather than a demonstrated sandbox escape.

The fix routes save_file's write through the same O_NOFOLLOW-protected helper already used by the upload path, so both File Manager write sinks carry identical kernel-enforced protection, and reports a symbolic-link refusal explicitly instead of surfacing the underlying system error text. Note that files created by save_file are now given mode 0600, inheriting the behaviour introduced for uploads. The protection covers the final path component; substitution of an intermediate directory component is not addressed by this change.

This issue affects pgAdmin 4: from the introduction of the containment check in the File Manager save path before 9.18.

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

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

File Manager save_file writes through a symbolic link planted after the containment check (CVE-2026-86861) · Issue #10385 · pgadmin-org/pgadmin4 · GitHub

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

Vendor Advisories for CVE-2026-86861(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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.

  1. 2026-09-19 18:29 UTCEG score recompute
  2. 2026-09-19 18:29 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:08 UTCGHSA enrichment
  5. 2026-09-17 20:27 UTCEG score recompute
  6. 2026-09-17 20:27 UTCGHSA enrichment
  7. 2026-09-17 19:20 UTCEG score recompute
  8. 2026-09-17 19:20 UTCGHSA enrichment
  9. 2026-09-17 17:57 UTCEG score recompute
  10. 2026-09-17 15:35 UTCEG score recompute
  11. 2026-09-17 15:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86861?
CVE-2026-86861 is a medium vulnerability published on September 17, 2026. pgAdmin 4's File Manager savefile endpoint, which backs saving from the Query Tool and ERD, validated the requested path with Filemanager.checkaccesspermission() and then opened the file for writing with a plain open() call. CVE-2026-7819 had previously hardened the separate file upload path by…
When was CVE-2026-86861 disclosed?
CVE-2026-86861 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86861 actively exploited?
CVE-2026-86861 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 62.4% of all scored CVEs.
What is the CVSS score of CVE-2026-86861?
CVE-2026-86861 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-86861?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86861, 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

Explore the affected products and dependency analysis for CVE-2026-86861

Explore →

Is Your Infrastructure Affected by CVE-2026-86861?

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