CVE-2026-56779

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

Score 6.4 from GitHub Security Advisory published 2026-06-25. a secondary CVSS source baseline 6.4; sources differ by 0.0.

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

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

MaxKB before 2.10.0 contains a server-side request forgery vulnerability in tool creation and update endpoints that allows authenticated users to make arbitrary server requests by supplying unvalidated downloadCallbackUrl and download_url parameters. Attackers with default workspace USER role can exploit this to access internal network services by providing malicious URLs to the ToolSerializer endpoints.

CVSS v3
6.4
EG Score
6.4(high)
EPSS
6.8%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit.
generic

MaxKB < 2.10.0 - Server-Side Request Forgery via downloadCallbackUrl and download_url Parameters | Advisories | VulnCheck

https://www.vulncheck.com/advisories/maxkb-server-side-request-forgery-via-downloadcallbackurl-and-download-url-parameters
generic🟡 PoC Available

[Security] Authenticated SSRF via unvalidated callback URL in tool import -- MaxKB v2.9.2 · Issue #6272 · 1Panel-dev/MaxKB · GitHub

https://github.com/1Panel-dev/MaxKB/issues/6272
github_commit Patch Available

commit 6c156afc656a (1Panel-dev/MaxKB)

Patch available: 1Panel-dev/MaxKB v2.10.0-lts (contains commit 6c156afc656a)

https://github.com/1Panel-dev/MaxKB/commit/6c156afc656afa62ea4280e504a06ac1c9696b36

Vendor Advisories for CVE-2026-56779(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 37× 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-07-06 19:47 UTCEG score recompute
  2. 2026-07-06 19:47 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 17:20 UTCEG score recompute
  8. 2026-07-05 17:20 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 14:58 UTCEG score recompute
  12. 2026-07-04 14:58 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 12:36 UTCEG score recompute
  16. 2026-07-03 12:36 UTCGHSA enrichment
  17. 2026-07-02 09:55 UTCEG score recompute
  18. 2026-07-02 09:55 UTCGHSA enrichment
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 07:35 UTCEG score recompute
  21. 2026-07-01 07:35 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 05:15 UTCEG score recompute
  24. 2026-06-30 05:14 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 12 more
  1. 2026-06-29 02:52 UTCEG score recompute
  2. 2026-06-29 02:52 UTCGHSA enrichment
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 00:31 UTCEG score recompute
  7. 2026-06-28 00:31 UTCGHSA enrichment
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 22:10 UTCEG score recompute
  10. 2026-06-26 22:10 UTCGHSA enrichment
  11. 2026-06-25 19:49 UTCEG score recompute
  12. 2026-06-25 19:49 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-56779?
CVE-2026-56779 is a medium vulnerability published on June 25, 2026. MaxKB before 2.10.0 contains a server-side request forgery vulnerability in tool creation and update endpoints that allows authenticated users to make arbitrary server requests by supplying unvalidated downloadCallbackUrl and download_url parameters. Attackers with default workspace USER role can…
When was CVE-2026-56779 disclosed?
CVE-2026-56779 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56779 actively exploited?
CVE-2026-56779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56779?
CVE-2026-56779 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-56779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56779, 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-56779

Explore →

Is Your Infrastructure Affected by CVE-2026-56779?

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

Start Free Scan →Browse All CVEs