CVE-2026-56257

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Capgo before 12.128.2 allows direct patching of public.apps.owner_org through PostgREST, bypassing the transfer_app() workflow and creating split-brain ownership. Attackers can directly update apps.owner_org while leaving app_versions.owner_org unchanged, enabling old-org keys to retain access to version data while new-org keys control the app record.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
8.0%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Direct PostgREST update of public.apps.owner_org bypasses transfer_app() and leaves app_versions.owner_org with the previous organization · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-v9jp-r5wh-qqcp
generic

Capgo - Authorization Bypass in App Ownership Transfer via Direct PostgREST Update | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-authorization-bypass-in-app-ownership-transfer-via-direct-postgrest-update

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 73× 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-15 18:50 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 06:12 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 17:36 UTCEG score recompute
  8. 2026-07-14 05:16 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 16:53 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 04:19 UTCEG score recompute
  14. 2026-07-12 15:41 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 03:20 UTCEG score recompute
  17. 2026-07-11 14:59 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 02:38 UTCEG score recompute
  21. 2026-07-10 14:17 UTCEG score recompute
  22. 2026-07-10 01:51 UTCEG score recompute
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 13:30 UTCEG score recompute
Show 48 more
  1. 2026-07-09 01:10 UTCEG score recompute
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-08 12:48 UTCEG score recompute
  5. 2026-07-08 00:23 UTCEG score recompute
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-07 12:02 UTCEG score recompute
  9. 2026-07-06 23:42 UTCEG score recompute
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 11:21 UTCEG score recompute
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 22:46 UTCEG score recompute
  16. 2026-07-05 10:24 UTCEG score recompute
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 22:04 UTCEG score recompute
  20. 2026-07-04 09:42 UTCEG score recompute
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 21:22 UTCEG score recompute
  24. 2026-07-03 09:02 UTCEG score recompute
  25. 2026-07-02 20:42 UTCEG score recompute
  26. 2026-07-02 08:19 UTCEG score recompute
  27. 2026-07-01 19:59 UTCEG score recompute
  28. 2026-07-01 15:07 UTCEPSS rescore
  29. 2026-07-01 07:39 UTCEG score recompute
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-30 19:18 UTCEG score recompute
  32. 2026-06-30 06:58 UTCEG score recompute
  33. 2026-06-29 18:35 UTCEG score recompute
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-29 14:06 UTCEPSS rescore
  36. 2026-06-29 06:15 UTCEG score recompute
  37. 2026-06-28 17:51 UTCEG score recompute
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 05:30 UTCEG score recompute
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-27 17:10 UTCEG score recompute
  43. 2026-06-27 04:50 UTCEG score recompute
  44. 2026-06-27 03:08 UTCEPSS rescore
  45. 2026-06-26 16:28 UTCEG score recompute
  46. 2026-06-26 04:08 UTCEG score recompute
  47. 2026-06-25 15:48 UTCEG score recompute
  48. 2026-06-25 15:47 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56257?
CVE-2026-56257 is a high vulnerability published on June 24, 2026. Capgo before 12.128.2 allows direct patching of public.apps.ownerorg through PostgREST, bypassing the transferapp() workflow and creating split-brain ownership. Attackers can directly update apps.ownerorg while leaving appversions.owner_org unchanged, enabling old-org keys to retain access to…
When was CVE-2026-56257 disclosed?
CVE-2026-56257 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update 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-56257 actively exploited?
CVE-2026-56257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56257?
CVE-2026-56257 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-56257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56257, 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-56257

Explore →

Is Your Infrastructure Affected by CVE-2026-56257?

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

Start Free Scan →Browse All CVEs