CVE-2026-56767

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Maxun before 0.0.42 contains a cross-tenant insecure direct object reference vulnerability in storage and webhook API handlers that allows authenticated users to access other users' robots and OAuth tokens. Attackers can read plaintext Google and Airtable access tokens, modify, delete, or execute other users' robots by bypassing ownership checks in API endpoints.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
24.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github_pr.
generic

Maxun < 0.0.42 - Cross-Tenant IDOR in Storage and Webhook API Handlers | Advisories | VulnCheck

https://www.vulncheck.com/advisories/maxun-cross-tenant-idor-in-storage-and-webhook-api-handlers
github_pr Patch Available

fix: multi-user data isolation

Patch available: getmaxun/maxun v0.0.42 (PR #1088 merged 2026-06-04)

https://github.com/getmaxun/maxun/pull/1088
generic

[Bug]: Cross-tenant IDOR leaks OAuth tokens and allows arbitrary modification/deletion · Issue #1079 · getmaxun/maxun · GitHub

https://github.com/getmaxun/maxun/issues/1079
github_commit Patch Available

commit 11db0257531f (getmaxun/maxun)

Patch available: getmaxun/maxun v0.0.42 (contains commit 11db0257531f)

https://github.com/getmaxun/maxun/commit/11db0257531f1c23dec94727793c9444ee2873cf

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56767?
CVE-2026-56767 is a high vulnerability published on June 25, 2026. Maxun before 0.0.42 contains a cross-tenant insecure direct object reference vulnerability in storage and webhook API handlers that allows authenticated users to access other users' robots and OAuth tokens. Attackers can read plaintext Google and Airtable access tokens, modify, delete, or execute…
When was CVE-2026-56767 disclosed?
CVE-2026-56767 was first published in the National Vulnerability Database on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56767 actively exploited?
CVE-2026-56767 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56767?
CVE-2026-56767 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56767?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56767, 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-56767

Explore →

Is Your Infrastructure Affected by CVE-2026-56767?

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

Start Free Scan →Browse All CVEs