CVE-2026-56279

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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 contains an information disclosure vulnerability in the get_orgs_v7(userid) RPC function that remains publicly invokable despite intended private access controls. Unauthenticated attackers can supply arbitrary user UUIDs to retrieve foreign users' organization membership, roles, management emails, and billing metadata.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
23.3%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (2)

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

Regression: private get_orgs_v7(userid) RPC remains anonymously invokable and leaks foreign users’ organization membership, roles, billing metadata, and management email · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-fch8-pp28-mw2x
generic

Capgo - Information Disclosure via get_orgs_v7 RPC Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-information-disclosure-via-get-orgs-v7-rpc-endpoint

Vendor Advisories for CVE-2026-56279(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 / 34× 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-16 01:27 UTCEG score recompute
  2. 2026-07-16 01:27 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 14:34 UTCEG score recompute
  6. 2026-07-15 14:34 UTCGHSA enrichment
  7. 2026-07-15 03:40 UTCEG score recompute
  8. 2026-07-15 03:40 UTCGHSA enrichment
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-14 16:45 UTCEG score recompute
  12. 2026-07-14 16:45 UTCGHSA enrichment
  13. 2026-07-14 05:52 UTCEG score recompute
  14. 2026-07-14 05:52 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 18:59 UTCEG score recompute
  17. 2026-07-13 18:59 UTCGHSA enrichment
  18. 2026-07-13 08:05 UTCEG score recompute
  19. 2026-07-13 08:05 UTCGHSA enrichment
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 21:12 UTCEG score recompute
  23. 2026-07-12 21:12 UTCGHSA enrichment
  24. 2026-07-12 10:17 UTCEG score recompute
  25. 2026-07-12 10:17 UTCGHSA enrichment
Show 9 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 23:24 UTCEG score recompute
  3. 2026-07-11 23:24 UTCGHSA enrichment
  4. 2026-07-11 12:31 UTCEG score recompute
  5. 2026-07-11 12:31 UTCGHSA enrichment
  6. 2026-07-11 01:38 UTCEG score recompute
  7. 2026-07-11 01:38 UTCGHSA enrichment
  8. 2026-07-10 14:43 UTCEG score recompute
  9. 2026-07-10 14:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56279?
CVE-2026-56279 is a high vulnerability published on July 10, 2026. Capgo before 12.128.2 contains an information disclosure vulnerability in the getorgsv7(userid) RPC function that remains publicly invokable despite intended private access controls. Unauthenticated attackers can supply arbitrary user UUIDs to retrieve foreign users' organization membership, roles,…
When was CVE-2026-56279 disclosed?
CVE-2026-56279 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56279 actively exploited?
CVE-2026-56279 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56279?
CVE-2026-56279 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56279?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56279, 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-56279

Explore →

Is Your Infrastructure Affected by CVE-2026-56279?

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

Start Free Scan →Browse All CVEs