Skip to content
major vulnerability· requires attention

Affects repository token model used across code-hosting/CI platforms; enables code/tamper of private PRs and supply-chain compromise impacting many organizations.

Cloud

CVE-2026-58443

9.1
Critical
EPSS 0.58%Patch availableAug 15, 2026

Public-only repo tokens can update private PR head branches, enabling code tampering.

common questions

Is CVE-2026-58443 being exploited?

Not confirmed. CVE-2026-58443 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.58% probability of exploitation in the next 30 days.

How severe is CVE-2026-58443?

CVE-2026-58443 is rated Critical with a CVSS score of 9.1. 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-58443?

Yes. A fix has been recorded for CVE-2026-58443. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58443 affect?

CVE-2026-58443 affects Public-only repository tokens (CI/CD), Pull request head branches (private PRs), Git hosting platforms / repository workflows, CI/CD pipelines using repo tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58443?

Revoke/rotate public repo tokens, restrict workflow permissions, and apply vendor patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Public-only repository tokens (CI/CD)Pull request head branches (private PRs)Git hosting platforms / repository workflowsCI/CD pipelines using repo tokens
impact

Allows attackers with public repo token access to modify private pull request head branches, enabling malicious commits, CI/workflow tampering, and supply-chain compromise.

action required

Immediate action required

affected versions
Gitea Gitea Open Source Git Server
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free