Bypasses token 'public-only' scope allowing access to limited-visibility repos/packages — risks widespread code/data exposure on popular code-hosting platforms.
CVE-2026-56443
Token 'public-only' scope bypass allows access to limited-visibility repos/packages.
Is CVE-2026-56443 being exploited?
Not confirmed. CVE-2026-56443 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-56443?
CVE-2026-56443 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56443?
Yes. A fix has been recorded for CVE-2026-56443. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56443 affect?
CVE-2026-56443 affects Code hosting platforms token scopes (repositories/packages), CI/CD systems using scoped tokens, Developer-managed API tokens/credentials. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56443?
Revoke/rotate affected tokens, audit and tighten scopes, monitor token usage, apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Tokens limited to 'public-only' can access limited-visibility repositories and packages, enabling data exfiltration, supply-chain compromise, and code tampering.
Immediate action required
- affected<= 1.26.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.